[Bug 16502] New: Define multiple monitor support and per-subdomain

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16502

           Summary: Define multiple monitor support and per-subdomain
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fullscreen
        AssignedTo: annevk@opera.com
        ReportedBy: warcraftthreeft@sbcglobal.net
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Currently the specification doesn't explain how browsers should attempt to
handle fullscreen across multiple monitors. This has led to implementations
simply releasing fullscreen or hiding a toggleable feature in their
configuration files to allow a webpage to preserve fullscreen.

A common use case is someone watching a video on one screen while working on
another screen. The expected scenario would be the user clicks on the other
screen removing focus. Now since the program has lost focus a security box - in
Firefox and Chrome, a yellow box - should display which asks the user if they
want to allow the page to stay in fullscreen.

I'd recommend putting a non-normative recommendations regarding this behavior.
The pointer lock handles this cleanly in their spec with the comment:
"Preferences per sub-domain can be used to allow or block pointer lock, similar
to pop-up, geolocation, and fullscreen."
- http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html

So this would be a per subdomain preference that most browsers would be
expected to implement for convenience. Currently for a normal user having to go
into the configuration to change a fullscreen preference just for watching a
video in another window is foreign to them. This change would greatly simplify
this for the common user without introducing any security problems.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Saturday, 24 March 2012 01:55:10 UTC