[Bug 21962] [Custom]: Running lifecycle callbacks should be integrated with microtask processing

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

--- Comment #4 from Dominic Cooney <dominicc@chromium.org> ---
(In reply to comment #3)
> (In reply to comment #0)
> Well, MutationObserver callback itself forms a microtask.

I'm going off "microtask checkpoint" as described here:
<http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#perform-a-microtask-checkpoint>

I must be missing something obvious here. From my reading of the spec,
implementations would:

1. Run lifecycle callbacks until they're exhausted.
2. Run MutationObservers until they're exhausted.
(Microtask checkpoint done.)

What happens to lifecycle callbacks that are scheduled during step 2? Before
the next checkpoint the document may go away, etc.

It seems this should instead be:

While there are lifecycle callbacks or mutation observations:
  While there are lifecycle callbacks
    Deliver lifecycle callbacks
  While there are mutation observations
    Deliver mutation observations

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

Received on Wednesday, 8 May 2013 12:33:34 UTC