22330 2013-06-12 00:28:17 +0000 [Custom]: Use consistent language for NAME and TYPE and NAME and EXTENDS 2013-06-18 19:47:34 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 89139 0 dominicc 2013-06-12 00:28:17 +0000 "NAME, the custom element name of the element being registered" In the description of register, NAME is a custom element name and EXTENDS is a local-name. However in the element registration algorithm, TYPE is the custom element name and NAME is a local name. The spec is correct, there's alpha-renaming of TYPE/NAME and NAME/EXTENDS. It is just *really* confusing when reading the spec to have TYPE and NAME refer to two different things in slightly different contexts. The Blink implementation uses TYPE for the thing that uniquely identifies the custom element. For custom tags, this is the tag name. For type extensions, this is the value of the "is" attribute. NAME is always the tag name of the custom element. For custom tags, TYPE and NAME have the same value. 89419 1 dglazkov 2013-06-17 22:17:44 +0000 Good point. I wonder if we should call it "custom element type" in the spec, too. 89424 2 dglazkov 2013-06-17 22:31:27 +0000 https://codereview.appspot.com/10340045 89500 3 dglazkov 2013-06-18 19:47:34 +0000 https://dvcs.w3.org/hg/webcomponents/rev/680e197157a5