Will any new features be tied to constructors?

Anne van Kesteren annevk at annevk.nl
Tue Jun 30 16:27:47 UTC 2015


On Tue, Jun 30, 2015 at 5:54 PM, Allen Wirfs-Brock
<allen at wirfs-brock.com> wrote:
> How would your hypothetical early allocated objects be observably exposed?

The design is basically that the browser first creates a "normal"
element, and at a later point changes the prototype and invokes the
callback. It's explained in some detail in this email:

  https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0230.html


> What's wrong with inserting a "deferred custom element" node into the DOM when you initially parse and then replacing it with an actual custom element instance of the correct class when when the script it depends upon has been loaded?

There's some rationale on this page:

  https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0230.html

In brief, you might lose added event listeners, gets complicated with
attributes and children, mutation observers will be somewhat spammy.
Domenic and Dimitry might be able to elaborate more.


-- 
https://annevankesteren.nl/


More information about the es-discuss mailing list