[Bug 17146] [Custom]: Constructor generation algorithm doesn’t create the right prototype chain

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

--- Comment #1 from Dimitri Glazkov <dglazkov@chromium.org> 2012-05-24 00:01:18 UTC ---
(In reply to comment #0)
> Specifically in this part:
> 
> "Create a new JavaScript object with BASE as prototype"
> 
> This is a ambiguous because BASE is described as "a DOM element which
> implements the HTMLElement interface." Is it an instance of a DOM element? Or
> the constructor like HTMLFooElement?
> 
> Anyway, the prototype of the new JavaScript object should be BASE.prototype, eg
> HTMLDivElement.prototype.
> 
> Probably more precise prose is required here because not all HTML elements have
> specific unique prototypes (eg INS, DEL both use HTMLModElement.)
> 
> Can I suggest replacing step 1 with language like:
> 
> Let BASEINTERFACE be the DOM Interface used by BASE.
> Create a new JavaScript object with BASEINTERFACE.prototype as the prototype.

This is tricky. We're trying to dance around the notion of DOM element
prototypes without naming them directly. I feel like the
BASEINTERFACE.prototype is a cop-out.

Could you not take var div = document.createElement('div') and treat it as a
prototype for a custom DOM element. Why not?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 24 May 2012 00:01:24 UTC