[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

--- Comment #13 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #12)

There's one somewhat nasty effect of this(In reply to comment #5)
> (In reply to comment #4)
> > - Maybe we could not bother doing prototype chain walking on register. If
> > the author wants to mess up prototype chains, let them.
> 
> wchen pointed out to me recently that because prototype chains are mutable,
> doing any sort of checking under document.register only gives hints to the
> authors at best. At worst, it prevents some overly-clever author from doing
> what he wants. Given that and the ambiguous prototype problem, it seems like
> we should basically just ignore the prototype for the purposes of document
> registration (except to associate the name with the prototype).

Just to keep my sanity and record this somewhere. There's a fun discord between
that explicit hint value (let's call it "type extension base value") and the
value of "extends" attribute in the declarative syntax:

1) The type extension base value is always identifying a built-in HTML/SVG
element.
2) The extends value could be both a built-in and custom element name.

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

Received on Wednesday, 29 May 2013 23:00:34 UTC