- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Jul 2014 08:57:09 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26366 Bug ID: 26366 Summary: It's possible to go fullscreen with an element not in the document Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux 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 This is one example of a class of problems caused by the checks made synchronously in requestFullscreen() not necessarily holding when the rest of the function runs async. To go fullscreen with an element not in the document: element.requestFullscreen(); element.parentNode.removeChild(element); To end up with a fullscreen element stack with siblings are put on the stack: element.requestFullscreen(); element.nextSibling.requestFullscreen(); I'm not sure what bad things can result, but it seems silly to make checks that aren't actually guaranteed to hold. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 17 July 2014 08:57:10 UTC