[whatwg] api for fullscreen()
jonas at sicking.cc
Thu Dec 17 00:32:34 PST 2009
On Thu, Dec 17, 2009 at 12:12 AM, Robert O'Callahan
<robert at ocallahan.org> wrote:
> 2009/12/17 Ian Fette (イアンフェッティ) <ifette at google.com>
>> I'm not convinced we actually need opt-in, though if we did have opt-in it
>> should allow the user to persist that choice (don't ask me for permission
>> each time i try to fullscreen a youtube video.)
>> I would much rather go for user gesture + opt-out. e.g. you have to cal
>> fullscreen() in response to a user gesture, you immediately get
> It's really easy to get users to click on things.
>> but maybe there's some dorky bar up top that stays around until you click
>> "go away" or "never put up the dork bar again for this site".
Technically speaking this isn't something that needs to be
standardized. All we need is a standardized fullscreen() function
somewhere, and possibly standardized "fullscreenon"/"fullscreenoff"
events. Browsers are free to implement whatever UI they want after
More information about the whatwg