20489 2012-12-22 00:33:40 +0000 [Custom]: Nothing ever defines what the "custom element name" of a random element is 2013-02-20 19:02:48 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED DUPLICATE 21063 P2 normal --- 17103 20684 1 bzbarsky dglazkov wchen public-webapps-bugzilla oldest_to_newest 80516 0 bzbarsky 2012-12-22 00:33:40 +0000 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. 80517 1 dglazkov 2012-12-22 00:35:45 +0000 (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. 80522 2 bzbarsky 2012-12-22 01:11:24 +0000 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? 80523 3 bzbarsky 2012-12-22 01:11:58 +0000 And in particular, the concept of "tag name" does not appear anywhere in http://dom.spec.whatwg.org/ 83413 4 dglazkov 2013-02-20 19:02:48 +0000 Pouring this over into bug 21063. *** This bug has been marked as a duplicate of bug 21063 ***