26626 2014-08-21 09:01:11 +0000 Populate the full list of event targets before firing any events 2014-08-26 12:59:48 +0000 1 1 1 Unclassified WebAppsWG Fullscreen unspecified PC Linux RESOLVED FIXED P2 normal --- 1 philipj annevk mike public-webapps public-webapps-bugzilla oldest_to_newest 110389 0 philipj 2014-08-21 09:01:11 +0000 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. 110391 1 philipj 2014-08-21 09:22:07 +0000 (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.) 110589 2 annevk 2014-08-26 09:32:27 +0000 https://github.com/whatwg/fullscreen/commit/d24852303d039fc227edf1b871259120d0c56ec3 110598 3 philipj 2014-08-26 12:59:48 +0000 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