On Wed, Sep 21, 2011 at 12:05 PM, Alexey Proskuryakov <ap@webkit.org> wrote:
21.09.2011, в 11:21, James Robinson написал(а):
one can always move the mouse pointer to top of screen to get back their menu bar. Is that a Mac thing?
Yes, this is how fullscreen applications regularly work on OS X.
This is not true for several Flash-based fullscreen video players that I've used on my mac. The interaction there is that upon entering fullscreen Flash displays an overlay indicating that hitting ESC will exit fullscreen mode and the video player displays its controls near the bottom of the screen. After these fade away, the video controls appear only when moving the mouse pointer to the bottom ~1/3rd of the screen. Moving the mouse pointer to the top of the screen does nothing. Hitting ESC or clicking on the appropriate button in the video player's controls exits fullscreen mode. This seems entirely reasonable to me, the keyboard control is provided by Flash itself to prevent bad SWFs from taking control of my computer and the SWF itself provides the additional controls that make sense for its domain.
You are describing how Flash exits full screen, and the fact that it apparently always has mouse lock in full screen (so you cannot get to browser menu bar by moving mouse pointer up). It's a different behavior from what this API provides.
Besides being a security measure for a subtly different feature, Flash behavior is quite annoying, and not very efficient - see e.g. < http://www.bunnyhero.org/2008/05/10/scaring-people-with-fullscreen/>.
To demonstrate the difference with Flash, there is no mouse lock in Safari fullscreen, so you can move the mouse pointer up to get the menu bar.
Anyway, I'm not sure if we already agreed that mouse lock is only desirable in full screen. I think that the spec has the goal of enabling it in browser windows.
21.09.2011, в 11:22, Darin Fisher написал(а):
basing APIs largely on how Windows used to work up to version 7 may not be
future proof.
Yes, but >90% of internet users are not familiar with Metro. They are familiar with Windows as it exists today (XP thru 7).
More than 90% is an understatement :)
Is your implication that Microsoft will be forced to make future Windows UI behave the same as Windows 7 does? Otherwise, it's not clear to me how a reference to old behavior is relevant to being future proof.
My point was that emulating the behavior that most users are familiar with will likely create a predictable user experience. Most users are familiar with hitting ESC to exit fullscreen, so it seems sensible to piggyback on that. By the way, wouldn't it be better to debate this API in the WebEvents WG? -Darin