[Bug 21886] [Custom]: Define or link to what it means for a local name to be associated with an interface

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

Dimitri Glazkov <dglazkov@chromium.org> changed:

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

--- Comment #6 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #5)
> It would have to be. I really don't like the magical "guess the name" APIs
> in general. Proposal A seems like the way to go.

If we're going with A, should the base element name be:

1) the second optional argument in document.register. The drawback here is that
for some values of options.prototype, the argument is _not_ optional, which is
somewhat confusing.

2) another option of ElementRegistrationOptions. The drawback here is that in
ES6, this will be just a static class member, and then people will be asking,
"why is that here?" And "why isn't name there as well?"

Also adding Scott, who comes with opinions.

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

Received on Tuesday, 21 May 2013 22:10:37 UTC