[Bug 22459] [Custom]: Consider explicitly emptying callback queue in more cases

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

--- Comment #16 from Scott Miles <sjmiles@chromium.org> ---
Imo, the algorithm should be naive and not try to resolve these timing issues.

I would expect something like:

  x-a enteredDocument
    x-c attributeChanged
  x-b enteredDocument
  x-c enteredDocument

I do realize that at 'attributeChanged' time, 'x-c' is ignorant about being in
an 'entered' state, but the callbacks have to occur serially and not having
simultaneous state knowledge is the price we pay for wanting to be
synchronous-like.

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

Received on Tuesday, 9 July 2013 02:00:19 UTC