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

[Bug 26479] New: Platform does not support fullscreen, could fullscreenEnabled be false?

From: <bugzilla@jessica.w3.org>
Date: Thu, 31 Jul 2014 10:51:50 +0000
To: public-webapps@w3.org
Message-ID: <bug-26479-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26479

            Bug ID: 26479
           Summary: Platform does not support fullscreen, could
                    fullscreenEnabled be false?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fullscreen
          Assignee: annevk@annevk.nl
          Reporter: igsolla@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

I wonder if it would be possible to change the spec so that fullscreenEnabled
is false if the platform does not support full screen. This is the first time
that I'm reviewing a standard, so I suspect that there is a reason why we can't
do that (if so, I'd be grateful if you could explain, thanks!).

The problem is that when the platform does not support fullscreen,
fulscreenEnabled
(http://fullscreen.spec.whatwg.org/#dom-document-fullscreenenabled) will return
true but the request to enter fullscreen will fail with an error
(http://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen) due to this
condition: "There is a previously-established user preference, security risk,
or platform limitation".

I think it would be better if fulscreenEnabled was false if we already know
that the platform does not support full screen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 31 July 2014 10:51:51 UTC

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