W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2011

[whatwg] Full Screen API Feedback

From: James May <whatwg@fowlsmurf.net>
Date: Thu, 12 May 2011 20:46:26 +1000
Message-ID: <BANLkTi=xkVyKbm4ousxwQ4DLpr5i_fS9xQ@mail.gmail.com>
Why can't the browser just do the "fullscreen in a window" behaviour
until/if the user approves?

No need for new events even, although a "fullscreen lost", sourced eg. from
some browser UI or loss of focus, might be useful.

I don't see why it would make a difference from the page's perspective
whether it would was actually taking up an entire screen or just all of a
certain window/tab. If the user wants the fullscreen ui without actually
being fullscreen, why stop them or allow pages to force them?


On 12 May 2011 18:42, timeless <timeless at gmail.com> wrote:

> On Thu, May 12, 2011 at 11:12 AM, Jer Noble <jer.noble at apple.com> wrote:
> > Okay, here's another proposal that should work with Firefox's passive
> permission system:
> >
> > Proposal:
> >
> > - Add a new boolean Element property "canRequestFullScreen".  This would
> map to Firefox's "Never" permission choice.
> > - Add the "fullscreendenied" event.  This would map to Firefox's "Not
> now" permission choice.
>
> Your proposal makes it fairly easy for sites to stick up annoying full
> content blocking "you must change your settings to proceed" elements.
>
> This is the wrong path.
>



-- 
-- James May
Received on Thursday, 12 May 2011 03:46:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:05 UTC