This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26587 - Element removal order is undefined in "fully exit fullscreen"
Summary: Element removal order is undefined in "fully exit fullscreen"
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Fullscreen (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-14 22:10 UTC by Philip Jägenstedt
Modified: 2014-08-15 10:40 UTC (History)
2 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2014-08-14 22:10:58 UTC
http://fullscreen.spec.whatwg.org/#model says:

3. Remove elements from doc's fullscreen element stack until there is one element left.

This doesn't say which elements to remove. WebKit/Blink currently removes all elements except the top element. The spec should do, because:

1. It doesn't cause document.fullscreenElement to change until the fullscreenchange event is fired.

2. If the top element was an iframe (no other element could be), the cross-document chain of fullscreen elements remains intact. Anything else can temporarily leave you with a gap in the chain. Having simple unbroken chains seems like a good invariant, then the implementation can assert it whenever pushing or popping to a fullscreen element stack and maybe prevent some bugs.
Comment 2 Philip Jägenstedt 2014-08-15 10:40:30 UTC
Thanks!