I'm not sure this makes sense to use futures exclusively. As a library author you want to know when the page transitions into full screen mode even if you didn't invoke the requestFullScreen call. Futures are also not extensible. With an event we could always tack on more information in the future. With Future<boolean> we're stuck with that boolean forever and can't add new information. It seems like there's a bit too much Future worshiping going on right now. On Thu, Apr 11, 2013 at 10:48 AM, Anne van Kesteren <annevk@annevk.nl>wrote: > On Thu, Apr 11, 2013 at 6:38 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > > Isn't the thing that matters whether _sites_ have it unprefixed? > > I don't know. I believe the browsers don't match each other exactly > either so there's probably some wiggle room. I suspect transitioning > at this point to be hard whatever we do, which is probably why it has > not happened yet. > > Also, we dispatch fullscreenchange to more than just the requesting > document. We could still get rid of fullscreenerror though and have > the simple non-iframe case be much more friendly towards developers. > > > -- > http://annevankesteren.nl/ > >
Received on Friday, 12 April 2013 10:32:21 UTC