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

[whatwg] Fullscreen Update

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 1 Nov 2011 09:46:05 +1300
Message-ID: <CAOp6jLbTfOR9e+sEz4FjWwjYsw9ZCrOgW_WeJ4Z3D1ZC3EsUfA@mail.gmail.com>
On Sat, Oct 29, 2011 at 10:47 PM, Robert O'Callahan <robert at ocallahan.org>wrote:

> I don't think punting on nested fullscreen is a good idea. It's not some
> edge case that most applications can't hit. For example, it will come up
> with any content that can go full-screen and can contain an embedded
> Youtube video. (It'll come up even more often if browser fullscreen UI is
> integrated with DOM fullscreen, which we definitely plan to do in Firefox.)
> If we don't support nested fullscreen well, then the user experience will
> be either
> -- making the video fullscreen while the containing content is already
> fullscreen simply doesn't work, or
> -- the video can go fullscreen, but when you exit fullscreen on the video,
> the containing content also loses fullscreen
>

Let me just clarify one thing. A browser's built-in "get out of
full-screen" user gesture will probably need to break out of all nested
fullscreen requests for security reasons. However, in-page UI to exit
full-screen (such as a button in pop-up video controls) should still be
able to return to the previous full-screen presentation.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive us
our sins and purify us from all unrighteousness. If we claim we have not
sinned, we make him out to be a liar and his word is not in us." [1 John
1:8-10]
Received on Monday, 31 October 2011 13:46:05 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:37 UTC