- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Jul 2013 02:02:30 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22459 --- Comment #17 from Dominic Cooney <dominicc@chromium.org> --- (In reply to comment #16) > 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. If I changed enteredCallback to createdCallback, would you change your mind? It is easier for the implementation to order the callbacks as uniformly as possible. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 9 July 2013 02:02:32 UTC