W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: Fullscreen API

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 9 Feb 2011 10:25:44 +1300
Message-ID: <AANLkTimnfHpW-jtm9wKpOyfy17kLnE4XLbnvi_+rc9a5@mail.gmail.com>
To: João Eiras <joao.eiras@gmail.com>
Cc: public-webapps <public-webapps@w3.org>
On Wed, Feb 9, 2011 at 9:12 AM, João Eiras <joao.eiras@gmail.com> wrote:

> On Tue, Feb 8, 2011 at 7:49 PM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> > 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.
>

You mean have the author set a class on the element? That requires more
author coding; removing the class would be tricky. Also, you can't handle
the case where an IFRAME (possibly cross-origin) wants to go full-screen ...
you'd need to set class values all the way up the document hierarchy.

Whether F11, double clicking, a context menu option, zooming or a
> gesture, are discoverable or not, it's a user agent UI issue,


I don't know of anything as discoverable as a button in the Web page next to
the rest of the video controls (for example).


> although
> a requestFullscreen() call could hint the UA that the webpage
> *suggests* going fullscreen, but then there is the spoofing/social
> engineering issue.
>

That's pretty much what the proposed spec says. It addresses (or permits
addressing) the spoofing issues reasonably well IMHO.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Tuesday, 8 February 2011 21:26:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT