26601 2014-08-18 22:09:55 +0000 Populate fullscreenElements later in requestFullscreen() 2014-08-26 11:57:51 +0000 1 1 1 Unclassified WebAppsWG Fullscreen unspecified PC All RESOLVED FIXED P2 normal --- 1 philipj annevk mike public-webapps public-webapps-bugzilla oldest_to_newest 110267 0 philipj 2014-08-18 22:09:55 +0000 http://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen fullscreenElements is populated synchronously, but before the animation frame task is run, the elements of fullscreenElements may have been moved in ways that still passes the ready checks, but leaves the resulting fullscreen element stacks inconsistent, for example if the pending element is moved between two iframes immediately after requestFullscreen() returns. The fix should be to populate the list of newly fullscreen elements in the animation frame task, immediately before pushing to stacks and firing events. Note that in such a rewrite, the ready check could be performed for only the pending element, since it is now recursive. 110584 1 annevk 2014-08-26 09:11:55 +0000 https://github.com/whatwg/fullscreen/commit/13e267c9bf275b645d4e7652e3acbc16f3dc5efb 110592 2 philipj 2014-08-26 11:57:51 +0000 LGTM and follow-up: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26671