This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Could do I guess. Want to solve this in HTML Ian if everyone is agreed?
I think Ignacio's suggestion is a good one. I suggest baking "There is a previously-established user preference, security risk, or platform limitation" into the definition of fullscreenEnabled and using that elsewhere in the spec, that ought to do it. I'm not sure why HTML would need to be involved, it just keeps track of the allowfullscreen attribute really...
HTML sets the "fullscreen enabled flag". I guess we could keep that mostly scoped to HTML's attribute though.
It looks very sensible. It seems that we could add that in the fullscreen specification. It would make sense actually given that the HTML logic is mostly related to the iframe sandboxing.
https://github.com/whatwg/fullscreen/commit/d35a070d443632d0071b49318e40092667ac9801
Looks great, thanks!