[Bug 26440] Allow fullscreenchange events to be synchronized with animation frames

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

--- Comment #17 from Philip Jägenstedt <philipj@opera.com> ---
Now that all events are fired in the same task, what happens when one event
handler rearranges the document tree? It looks like it's all in order, but
maybe for extra clarity a descendantDocs set could be populated and iterated in
two separate steps? It would be easy to overlook when implementing step 9.4,
and could in the worst case lead to documents with a non-empty fullscreen
element stack being left behind.

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

Received on Sunday, 3 August 2014 21:13:16 UTC