This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22330 - [Custom]: Use consistent language for NAME and TYPE and NAME and EXTENDS
Summary: [Custom]: Use consistent language for NAME and TYPE and NAME and EXTENDS
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency treegraph
 
Reported: 2013-06-12 00:28 UTC by Dominic Cooney
Modified: 2013-06-18 19:47 UTC (History)
0 users

See Also:


Attachments

Description Dominic Cooney 2013-06-12 00:28:17 UTC
"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.
Comment 1 Dimitri Glazkov 2013-06-17 22:17:44 UTC
Good point. I wonder if we should call it "custom element type" in the spec, too.
Comment 2 Dimitri Glazkov 2013-06-17 22:31:27 UTC
https://codereview.appspot.com/10340045
Comment 3 Dimitri Glazkov 2013-06-18 19:47:34 UTC
https://dvcs.w3.org/hg/webcomponents/rev/680e197157a5