Re: Fullscreen API

On Tue, Feb 8, 2011 at 7:49 PM, Robert O'Callahan <> wrote:
> On Wed, Feb 9, 2011 at 7:53 AM, Joćo Eiras <> wrote:
>> Detecting fullscreen is something that belong 100% to media queries.
>> Opera for instance, applies the "projection" media when the web page
>> is rendered fullscreen. So, the CSS stuff in the Mozilla  spec should
>> be replaced with proper media queries, and the fullscreenchange event
>> replaced with media query events.
> The :full-screen-document pseudo-class could be replaced with a media query,
> and that's probably a good idea. Thanks! The :full-screen pseudo-class
> cannot since it applies to "the full-screen element", and media query state
> is per-document.

That works just as fine if a class is used.

>> Regarding the web page requesting full screen access, I regard it as
>> dangerous, disruptive and unnecessary. If element ought to be rendered
>> fullscreen, they can be styled with
>> "position:fixed;top:0;left:0;width:100%;height:100%;z-index:1000".
>> Then if the UA user wishes, he/she can toggle the browser to go
>> fullscreen (F11 in any browser), else content just fits the viewport.
> Like it or not (and I don't!), Web developers are used to having in-page
> fullscreen UI because Flash provides it, and users are used to finding it
> there. It's also generally more discoverable than F11 or whatever the
> browser UI is. So there does need to be a way for the page to request
> full-screen.

Whether F11, double clicking, a context menu option, zooming or a
gesture, are discoverable or not, it's a user agent UI issue, although
a requestFullscreen() call could hint the UA that the webpage
*suggests* going fullscreen, but then there is the spoofing/social
engineering issue.

Received on Tuesday, 8 February 2011 20:12:41 UTC