[whatwg] Fullscreen Update
joaoe at opera.com
Wed Oct 19 08:49:07 PDT 2011
On Wed, 19 Oct 2011 17:31:40 +0200, Glenn Maynard <glenn at zewt.org> wrote:
> On Wed, Oct 19, 2011 at 11:00 AM, João Eiras <joaoe at opera.com> wrote:
>> I think you just solved your own issue :) Your if check is wrong given
>> use case.
> No, that's missing the point. These obscure corner cases should be
> minimized (in any API, and especially web APIs). People won't know to
> them, and everyone's browsing experience will be buggier when in
> Can anyone suggest a use case for having fullscreen be true when in
> (F11) fullscreen? I can't think of any.
> Besides, if the developer failed to test, it would just require an extra
> It wouldn't work at all. The exitFullscreen call would fail or no-op
> can't exit F11 fullscreen with this API, of course; it's not yours to
> so the next click would just call exitFullscreen again.
F11 and document.requestFullscreen() should produce exactly the same
results, so, document.fullscreen would be enabled. And there's no reason
not to (and otherwise would make the spec needlessly more complex).
More information about the whatwg