This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://fullscreen.spec.whatwg.org/#dom-document-exitfullscreen 9.6. If exitDocs's last document has a browsing context container, let topDoc be that browsing context container's node document, and then remove the top element from topDoc's fullscreen element stack and fire an event named fullscreenchange on topDoc. The event handlers already fired in these steps can have moved the iframe element of exitDocs's last document, so that the fullscreenchange event ends up firing on a document other than the document that the iframe went fullscreen in. It looks like moving part of step 9.6 to 9.3 and letting step 9.5 fire all of the events should fix this. It would also be nice if step 9.4 were also more explicit about first creating a list of documents and then firing events. For requestFullscreen(), bug 26601 should solve the problem.
(In reply to Philip Jägenstedt from comment #0) > It would also be nice if step 9.4 were also more explicit about first > creating a list of documents and then firing events. This bit looks like it shouldn't matter much because event handlers can't synchronously modify the fullscreen element stack, but they can change the tree order of the documents. (Test cases for this will be fun.)
https://github.com/whatwg/fullscreen/commit/d24852303d039fc227edf1b871259120d0c56ec3
LGTM and some follow-up: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26672 https://www.w3.org/Bugs/Public/show_bug.cgi?id=26673