This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The upgrade algorigthm says: "For each element ELEMENT in TREE whose custom element name is NAME: " but nothing defines, for an arbitrary element, what its custom element name is, as far as I can tell. What might make the most sense here, in my opinion, is looking for elements whose namespace is the HTML namespace and whose localName is NAME. Unless NAME can be non-lowercase here, in which case things are a bit more complicated.
(In reply to comment #0) > The upgrade algorigthm says: > > "For each element ELEMENT in TREE whose custom element name is NAME: " > > but nothing defines, for an arbitrary element, what its custom element name > is, as far as I can tell. It's defined here (even linked from the sentence you selected)? http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html#dfn-custom-element-name > > What might make the most sense here, in my opinion, is looking for elements > whose namespace is the HTML namespace and whose localName is NAME. Unless > NAME can be non-lowercase here, in which case things are a bit more > complicated.
No, that doesn't define it. That defines the syntax of a custom element name. It says nothing about how to extract one from a DOM node. Note, specifically, that "element's tag name" is not defined in the text you cite. Do you mean the DOM .tagName? Or something else?
And in particular, the concept of "tag name" does not appear anywhere in http://dom.spec.whatwg.org/
Pouring this over into bug 21063. *** This bug has been marked as a duplicate of bug 21063 ***