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

[Bug 26602] New: Cross-process damage control in requestFullscreen() and exitFullscreen()?

From: <bugzilla@jessica.w3.org>
Date: Mon, 18 Aug 2014 22:20:26 +0000
To: public-webapps@w3.org
Message-ID: <bug-26602-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26602

            Bug ID: 26602
           Summary: Cross-process damage control in requestFullscreen()
                    and exitFullscreen()?
           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

Here's an idea that doesn't fix any bug but may be worthwhile.

In requestFullscreen(), wait with the first ready check until just before the
resize, so that if it requires IPC, that won't have to be done synchronously
before requestFullscreen() returns. "Fullscreen is not supported" could be
moved as well, just in case establishing that actually requires inspecting each
document. Together with bug 26601 that should leave nothing fancy in the
synchronous section.

In exitFullscreen(), return immediately after step 1 or 2, or otherwise move
the population of parentDocs to the async section.

WDYT?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 18 August 2014 22:20:28 UTC

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