On 10/15/2011 07:27 AM, Anne van Kesteren wrote:
I wrote up a draft:
http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html
Defining when exactly the "fullscreen enabled" flag is set for Document
objects I will leave up to HTML. As well as defining the
"allowfullscreen" attribute. Presumably it should be set for Document
objects associated with the top-level browsing context and descendant
browsing context as long as their browsing context container has the
aforementioned attribute set.
If we want to transition from fullscreen when navigating, HTML can
define that as well, neatly integrated in the navigation section. The
"Model" section of the Fullscreen specification has an appropriate hook.
I have not added the key restrictions given earlier emails.
Unfortunately there was not that much feedback on them, but maybe this
draft will help on that front!
I went with "fullscreen" rather than "full screen" as that seemed
cleaner and easier to type. I also used "enter" and "exit" rather than
"request" and "cancel" as they seemed somewhat nicer too. I'm less
attached to this latter change though.
To me "enterFullscreen()" sounds like something which couldn't fail.
"requestFullscreen()" is closer to what actually happens: script asks
UA to go to fullscreen mode, but it may fail if user or UA for some
reason denies the request.
-Olli
