794468 - Fullscreen API and 'F11 Fullscreen' behaviours are inconsistent

Status: UNCONFIRMED

(Firefox :: Keyboard Navigation, defect)

Description

[quentind]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

Not sure if it is intended or not but the behaviour of Fullscreen API and 'F11 Fullscreen' are not consistent.

For instance, F11 Fullscreen doesn't trigger any event. Enabling/disabling Fullscreen mode with F11 and with the API doesn't work in as you would expect.

This will most likely cause issues when developing HTML5 games or any fullscreen enabled application.


Actual results:

Examples:

- Go to http://robnyman.github.com/fullscreen/
- Click on the 'fullscreen' button. => Fullscreen mode is on and background become red => OK, works as intended
- Press escape or F11 or click on the 'cancel fullscreen' button => OK, works as intended
- Now, press F11 => fullscreen is on but page background remains yellow. html:-moz-full-screen { background: red; } doesn't work.
- With F11 Fullscreen still enabled, click on the 'fullscreen' button => Background become red.
- With F11 Fullscreen still enabled, click 'cancel fullscreen' => Nothing happens.


Issues:
1: You can't cancel fullscreen mode programmaticaly if it has been toggled on with F11
2: When triggered with F11 no event is fired and CSS ':-moz-full-screen' is not supported.
3: You can toggle fullscreen mode with the JS API when F11 fullscreen is already on. This leads to confusion for developers as well as for users.
4: To cancel fullscreen mode with their keyboard, users need to press either ESC or F11 depending on how they enabled fullscreen mode. This is confusing.
5: Lets say you are creating a game and would like to offer fullscreen mode to your players. As far as i am aware, you cannot keep track of whether the fullscreen mode is enabled or not since F11 fullscreen doesn't trigger events. So for instance you can not reliably change the visual aspect of your fullscreen button accordingly (like with a 'toggle on' icon and a 'toggle off' icon).


Expected results:

I think the Fullscreen API and F11 fullscreen should behave the same.

FWIW, F11 fullscreen and API Fullscreen behave inconsistently in Webkit too.

Comment 1

[quentind]

Seems that we can't edit a bug description.

Sorry about the terrible grammar and writing.

Comment 2

[james]

I am also running into this problem.

"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0"

Comment 3

[David Goemans]

I can confirm that this happens. F11 behavior has an animation and doesn't seem to be consistent with the fullscreen API. We're building games using this, and Firefox is the only major browser that is showing issues with fullscreen.