[Bug 23206] [Custom]: The base element queue doesn't prevent custom element processing running ahead of imports

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

--- Comment #3 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to Dominic Cooney from comment #1)

In spec, I think I can express this in just a few sentences. Let me give it a
shot.

> Commentary:
> 
> There are complicating factors motivating this craziness:
> 
> - <link rel="import" ...> can be inserted and removed, bringing multiple
> documents into existence as it does so (I think?) so we need the document
> queue as a catch-all to make sure we eventually start calling people's
> callbacks.

Adding and removing import links imperative means that:
1) we're no longer operating on base element queue, and
2) all fetches are synchronous

This helps greatly, since this makes all these operations atomic and we don't
need to worry about stability of order (or ordering at all).

> - <link rel="import" ...> doesn't necessarily have an associated document,
> so we need to use the link tags themselves to keep track of things.
> 
> The ordering is going to be defined, but extremely wild, if you move a link
> tag (particularly to a different document.) The wildness if because we use a
> link tag to find a document to recurse to, but that might not be the one
> begotten from that insertion; time might have marched on? You get what you
> deserve.

I think it's same as above. I could be wrong. This is complicated stuff :)

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

Received on Wednesday, 11 September 2013 21:10:07 UTC