[w3c/webcomponents] [IDEA] Asynchronous upgrade. (#559)

I'm not sure if upgrade is async in the new spec, but in v0 in Chrome it appears not to be (at least that is my guess based on the hacks I've described in #558.

Here I propose that Custom Element class registration should not cause immediate upgrade, and should wait for the next turn, at which point the engine can upgrade elements in depth-first order.

I believe that this may possibly prevent me from requiring the hacks described in #558.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/559