W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

[webcomponents]: Custom element constructors are pinocchios

From: Dimitri Glazkov <dglazkov@google.com>
Date: Fri, 8 Mar 2013 11:27:19 -0800
Message-ID: <CADh5Ky0KVhYFMFeFY+B0spuGbKy_tL+MukT9LYR5qk7nNe1XeA@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>
Cc: Scott Miles <sjmiles@google.com>, Erik Arvidsson <arv@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>, William Chen <wchen@mozilla.com>, Blake Kaplan <mrbkap@mozilla.com>
As I started work on the components spec, I realized something terrible:

a) even if all HTML parsers could run script at any point when
constructing tree, and

b) even if all JS engines supported overriding [[Construct]] internal
method on Function,

c) we still can't make custom element constructors run exactly at the
time of creating an element in all cases,

d) unless we bring back element upgrade.

Here's why:

i) when we load component document, it blocks scripts just like a
stylesheet (http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#a-style-sheet-that-is-blocking-scripts)

ii) this is okay, since our constructors are generated (no user code)
and most of the tree could be constructed while the component is

iii) However, if we make constructors run at the time of tree
construction, the tree construction gets blocked much sooner, which
effectively makes component loading synchronous. Which is bad.

I see two ways out of this conundrum:

1) Give up on custom element constructors ever meeting the Blue Fairy
and becoming real boys, thus making them equivalent to readyCallback

* Now that readyCallback and constructor are the same thing, we could
probably avoid a dual-path API in document.register

* constructors are not real (for example, when a constructor runs, the
element is already in the tree, with all of the attributes set), so
there is no pure instantiation phase for an element

2) resurrect element upgrade

* constructors are real

* rejiggering document tree during upgrades will probably eat all (and
then some!) performance benefits of asynchronous load


Received on Friday, 8 March 2013 19:27:52 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:52 UTC