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

[Bug 26673] New: Append topDoc to exitDocs?

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 Aug 2014 12:59:25 +0000
To: public-webapps@w3.org
Message-ID: <bug-26673-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26673

            Bug ID: 26673
           Summary: Append topDoc to exitDocs?
           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

http://fullscreen.spec.whatwg.org/#dom-document-exitfullscreen

Since the same thing is done with topDoc as with exitDocs, it would be nice to
replace the topDoc bits with e.g. "If exitDocs's last document has a browsing
context container, append that browsing context container's node document to
exitDocs." after the resize check.

It also looks like it's possible for topDoc to have an empty fullscreen element
stack at this point. Start with a top-level document with a div and an iframe
on its stack, and a fullscreen element inside the iframe too. Calling
iframe.contentDocument.exitFullscreen() will schedule the animation frame task
steps, but resize will be false. If the iframe is moved to another document
with nothing on its fullscreen element stack before those steps run, we
shouldn't fire any events on that document. It probably doesn't matter how we
deal with this situation, "fully exit fullscreen" seems fine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 26 August 2014 12:59:26 UTC

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