[whatwg] api for fullscreen()
dion at almaer.com
Thu Dec 17 08:57:35 PST 2009
I love the idea of fullscreen() and on* events for developers and letting
the browsers come up with smart ways to do as much as they can to protect
users (as they have done countless times before with popups, phishing, etc).
We can't say no to every feature because "some poor user may click on
something by mistake" else we will have a weak platform. We need to do what
we can to educate and help as much as possible in the browsers.
Following Flash blindly doesn't have to be good, but Flash *does* have great
features for users and we shouldn't be blind to what they offer as a
platform and take the best parts (and make it better).
On Thu, Dec 17, 2009 at 3:33 AM, Aryeh Gregor
<Simetrical+w3c at gmail.com<Simetrical%2Bw3c at gmail.com>
> 2009/12/17 Jonas Sicking <jonas at sicking.cc>:
> > I guess that if you enforced that fullscreen could only happen in
> > response to a click then you are in better shape.
> Browsers already have heuristics just like this for opening popup
> windows, don't they? They seem to work pretty well to prevent pages
> from being too annoying. I don't think going out of fullscreen is any
> more annoying than closing a popup, so I think the only issue is
> Requiring a click doesn't seem like it would do anything to stop
> spoofing, though. You could just put an onclick handler on the body.
> Users click on the page all the time, to follow links or select text.
> Spoofing seems like a hard problem for general-purpose full-screening.
> 2009/12/17 Ian Fette (イアンフェッティ) <ifette at google.com>:
> > maybe there's some dorky
> > bar up top that stays around until you click "go away" or "never put up
> > dork bar again for this site".
> So they only have to get you to watch one fullscreen video on their
> site and reflexively dismiss the dork bar before they can spoof you?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg