W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

[Bug 26587] New: Element removal order is undefined in "fully exit fullscreen"

From: <bugzilla@jessica.w3.org>
Date: Thu, 14 Aug 2014 22:10:58 +0000
To: public-webapps@w3.org
Message-ID: <bug-26587-2927@http.www.w3.org/Bugs/Public/>

            Bug ID: 26587
           Summary: Element removal order is undefined in "fully exit
           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/#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.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 14 August 2014 22:11:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC