Bug 121496 – webkitRequestFullScreen with ALLOW_KEYBOARD_INPUT does not allow inputs

• Status: RESOLVED
• Resolution: WONTFIX
• Component: WebKit Misc.

[Allan Jardine]

Created attachment 211913 [details]
Page showing the inability to go full screen with ALLOW_KEYBOARD_INPUT

The documentation for webkitRequestFullScreen on the Apple web-site says that we should be able to pass in Element.ALLOW_KEYBOARD_INPUT into webkitRequestFullScreen to allow keyboard input when fullscreen. This is not the case - we don't even get as far as trying to enter text in full screen, we simply don't go full screen at all.

[Jer Noble]

This is intentional; the ability to accept alphanumeric keyboard events in full screen mode is considered a security risk, and the Apple port has disabled this feature.  The Safari developer documentation is (unfortunately) out-of-date.

Additionally, the most recent draft of the Fullscreen API spec <https://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html> has removed the `flags` parameter from Element.requestFullScreen().

[Allan Jardine]

Thanks for the feedback!

Is there any way to know that an input has been blocked? An event being fired in Javascript perhaps? At the moment, users of my application (video based, so it leads itself to full screening) will simply here a system alert and see there input not being entered. An event would at least let me tell them that Safari is blocking the input.

[Jer Noble]

(In reply to comment #2)
> Thanks for the feedback!
> 
> Is there any way to know that an input has been blocked? An event being fired in Javascript perhaps? At the moment, users of my application (video based, so it leads itself to full screening) will simply here a system alert and see there input not being entered. An event would at least let me tell them that Safari is blocking the input.

No, there isn't an error message generated. (A clever attacker could use those error events; we just eat them silently instead.)

[Jon]

 > No, there isn't an error message generated. (A clever attacker could use
> those error events; we just eat them silently instead.)

Wouldn't it be better to ask the user for permission to go full screen, and allow text input after that?

As is, it really limits the web apps you're able to build without being able to use text input.

I also tried using the js prompt function to request data while full screen. That did not end well at all in Safari.

You can see here: http://www.jonathanlaliberte.com/fullscreentest.html

It works well in Firefox and Chrome, but in Safari it seems to lock up the current tab.