- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Aug 2014 22:09:55 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26601
Bug ID: 26601
Summary: Populate fullscreenElements later in
requestFullscreen()
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Fullscreen
Assignee: annevk@annevk.nl
Reporter: philipj@opera.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 18 August 2014 22:09:56 UTC