[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 #2 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to Dominic Cooney from comment #0)
> Maybe I just don't understand the set of related specs well enough, but I
> don't see anything which stops custom element processing in a given document
> running ahead of imports in that document. The base element queue is sorted,
> and things are enqueued in it in a certain order, but it is unclear given:
> 
> <x-a>
> <link rel="import" href="two.html">
> <x-b>
> 
> two.html:
> ...
> <x-c>
> ...
> 
> that x-a, x-b, x-c isn't a valid order provided that x-a, x-b are run at one
> microtask checkpoint and x-c is run at another.

You're right! If:

1) the queue is in this state: [ x-a, @, x-b ], where "@" is the import that
has not loaded,
2) parser yields and the microtask checkpoint occurs,
3) the callbacks for x-a and x-b will be invoked, and x-c will be invoked
later.

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

Received on Wednesday, 11 September 2013 17:32:19 UTC