On Tue, 18 Oct 2011 23:24:27 +0900, Glenn Maynard <gl...@zewt.org> wrote:
Do you mean the user-fullscreen mode that most browsers enter with F11?
Not necessarily. You run into the same issue with requestFullscreen() usage.
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.)
I think it would be kind of nice if the UI and API-based fullscreen were aligned. Otherwise you run into all kinds of odd situations.
E.g. API-based fullscreen first. Then via native <video> controls you go UI-based fullscreen for a <video> displayed on that page. What happens when you exit? You can have the same scenario the other way around, or both can be done using solely the UI, or both can be done using solely the API. It would be confusing to users I think if you got different results here.
-- Anne van Kesteren http://annevankesteren.nl/
