- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Jul 2015 15:04:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27674 --- Comment #23 from Philip Jägenstedt <philipj@opera.com> --- (In reply to Domenic Denicola from comment #22) > This is always a bit tricky, but given that promises run on the microtask > queue, and you queue a task to fire fullscreenchange, you should be able to > get the promise callbacks to fire before the fullscreenchange listeners, > which will be early enough. As long as you just do "resolve the promise" > instead of "queue a task to resolve the promise" you'll be fine. Actually it isn't "queue a task to fire an event named fullscreenchange" any longer, but just "fire an event named fullscreenchange" inside "as part of the next animation frame task, run these substeps." That was done in order to get the timing of the events right. So there's a risk that if the promise is resolved at the same time as those events are fired (not queued), the callbacks for that will be run too late. However, this is all actually undefined right now because "animation frame task" isn't defined anywhere. Quite possibly it should be defined to be followed by a microtask checkpoint then, but as a matter of implementation I think that's all now in V8, so how? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 15 July 2015 15:04:04 UTC