[whatwg] api for fullscreen()
Ian Fette (イアンフェッティ)
ifette at google.com
Wed Dec 16 23:54:01 PST 2009
2009/12/16 Robert O'Callahan <robert at ocallahan.org>
> 2009/12/17 Ian Fette (イアンフェッティ) <ifette at google.com>
>> I think what I've heard from application developers over and over again is
>> that, while the UA may provide some way to go into full screen from in the
>> browser chrome, it is much more discoverable when that capability exists
>> from within the content area (e.g. people are used to clicking on the full
>> screen button in YouTube, and when you take that away users can no longer
>> figure out how to go full screen).
> We are also hearing this.
> Michael Dale's suggestion of using a passive, opt-in notification for this
> sounds reasonable to me.
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 fullscreened, 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".
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg