- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 26 Apr 2017 10:05:14 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 26 April 2017 17:05:51 UTC
> Those are the variants you would actually use internally, as you don't want to use setAttribute() which is rather odd when it comes to namespaces. What do you mean "internally"? Looking at e.g. [Ember](https://github.com/glimmerjs/glimmer-vm/blob/7708feacbd3c7b72ec725283b365760a0e141fd4/packages/%40glimmer/runtime/lib/dom/helper.ts#L107) or [React](https://github.com/facebook/react/blob/b1768b5a48d1f82e4ef4150e0036c5f846d3758a/src/renderers/dom/shared/DOMPropertyOperations.js#L158-L167) it seems like everyone branches on whether they're supplied a namespace by their caller (presumably only for SVG cases) and uses setAttribute instead. > HTML elements care too. Say more. I would have thought that after all the trouble we went through to try to simplify Attrs, at least one of the changes that might have stuck was making their namespace APIs have no effect (but still be around for back-compat). I guess not. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/449#issuecomment-297477372
Received on Wednesday, 26 April 2017 17:05:51 UTC