[Bug 24020] [Custom]: A tag name should be associated with the constructor and not the prototype

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

Dominic Cooney <dominicc@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dominicc@chromium.org

--- Comment #1 from Dominic Cooney <dominicc@chromium.org> ---
I think this should be addressed in Level 2 of the Custom Elements spec, or in
a related spec. Chrome is not in a position to implement this now.

The current implementation in Chrome associates the registered element name
with the generated constructor. This is effectively the same data as the
constructorToNameMap. So I think Chrome would have no problem implementing
requirements based on your proposal.

I do not think the specification needs to be as literal as the JavaScript you
have provided here, but it is a good informative sketch.

I think that the requirement that registering a Custom Element with a prototype
that is an interface prototype object should be relaxed to allow multiple
element names to share a prototype as is the case with built-in elements like
HTMLHeadingElement, etc. Perhaps misuse of a built-in interface prototype
object should be disallowed, however Chrome would not have a problem with a
completely laissez-faire approach.

Relaxing the interface prototype object restriction would be a
forward-compatible change because it makes errors into non-errors.

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

Received on Sunday, 8 December 2013 00:32:30 UTC