- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Aug 2014 10:55:28 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26568
Bug ID: 26568
Summary: Nothing stopping mis-nested fullscreen in iframes?
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
Let's say we have two sibling iframes, iframe1 and iframe2, and that they're
same-origin. First enter fullscreen with an element inside iframe1. Then
request fullscreen for an element inside iframe2. Since iframe2's document's
fullscreen element stack is empty, it seems like nothing's stopping it from
going fullscreen.
You will end up with a cross-document set of fullscreen elements that isn't a
simple chain, but a tree, which seems weird. Some check on ancestor browsing
contexts is probably needed in the fullscreen element ready check.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 13 August 2014 10:55:30 UTC