[Bug 20189] [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded

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

Dominic Cooney <dominicc@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dominicc@chromium.org

--- Comment #5 from Dominic Cooney <dominicc@chromium.org> ---
(In reply to comment #4)
> So... here's what I am planning. 
> 
> 1) The HTML Imports and Custom Elements specs will be written in a way that
> ensures that by the time the rendering engine starts running script in the
> document, all of the custom elements would have already been upgraded.

To split hairs--all custom elements that could be upgraded have been upgraded.

> 2) Technically, this means that we don't need the DOMElementsUpgraded
> events, because there's no way for a script to see them in the pre-upgraded
> state.
> 
> 3) However, I can totally see how it would be impossible to polyfill this.
> So, perhaps we should still have this event, and it would be spec'd to fire
> just before the first <script> element block is to be executed by the parser.
> 
> WDYT?

I don't think that this is a good idea; won't this mean major surgery to
implementations requiring much more speculative parsing? For example, what does
this do?

<!DOCTYPE html>
<script>
document.write('You\'re telling me I don\'t run yet?');
</script>
<link rel="import" ...>
<x-a>...

Does it process the import, maybe call x-a's readyCallback, and then rewind
things to run the first script block and do the document.write? Seems like
crazymaking.

So if you *do* run that script block first (you should!) then polyfilling this
is possible; it just means you need to pull in your polyfill before your first
<link rel="import" ...>.

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

Received on Wednesday, 22 May 2013 03:49:33 UTC