[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 #5 from Blake Kaplan <mrbkap@gmail.com> ---
(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).

> There's also the question of whether doing something ambiguous like
> extending HTMLModElement, HTMLHeadingElement. Is that an error?

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.

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

Received on Friday, 17 May 2013 22:35:26 UTC