[Bug 22330] New: [Custom]: Use consistent language for NAME and TYPE and NAME and EXTENDS

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22330

            Bug ID: 22330
           Summary: [Custom]: Use consistent language for NAME and TYPE
                    and NAME and EXTENDS
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: dominicc@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

"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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 12 June 2013 00:28:19 UTC