- From: Darin Fisher <darin@chromium.org>
- Date: Tue, 18 Oct 2011 15:52:45 -0700
On Tue, Oct 18, 2011 at 7:24 AM, Glenn Maynard <glenn at zewt.org> wrote: > On Tue, Oct 18, 2011 at 3:55 AM, Anne van Kesteren <annevk at opera.com> > wrote: > > > However, I just realized this does not work for the single document case. > > You have a video player website and you host your videos in <video> or > maybe > > a <div> container. So your video player website is displayed fullscreen, > > because your users like the fullscreen application feel from their OS, > but > > then they click to display one of those videos fullscreen and once they > hit > > exit the video player website is also no longer displayed fullscreen. > > > > Do you mean the user-fullscreen mode that most browsers enter with F11? > That's a separate piece of state entirely, since it affects the whole > browser window, not individual tabs. (You should still be able to > enterFullscreen and exitFullscreen, to set and clear the fullscreen > element. It just wouldn't change the browser window's actual fullscreen > status.) > > In Chrome, the user-fullscreen mode you get when you press F11 places the active tab into fullscreen mode. It is interesting to wonder how this API should interact with user-fullscreen mode. However, maybe that is best left to the UAs and shouldn't be covered by this spec. -Darin
Received on Tuesday, 18 October 2011 15:52:45 UTC