Commit afbe64d3 authored by scheib's avatar scheib Committed by Commit bot

Update HTML5 fullscreen/pointerlock documentation re: ESC handling.

Indicate the special handling of ESC key and the permissions
required to enter fullscreen/pointerlock and override ESC.

Review URL: https://codereview.chromium.org/738673003

Cr-Commit-Position: refs/heads/master@{#305128}
parent 5f13a0ef
......@@ -46,9 +46,14 @@ E.g. window.open(someUrl). --></dd>
<ul>
<li>In Chrome Apps, fullscreen is entered without
prompting the user or providing exit instructions.
Also, there is no default exit behavior. In normal webpages,
the browser intercepts the ESC key to exit fullscreen.
This behavior is not present in Chrome Apps.</li>
HTML5 fullscreen requires the <code>app.window.fullscreen</code>
permission in the manifest.
In normal webpages, the browser intercepts the ESC key to exit
pointer lock ensuring a consistent escape method for users.
That is also the behavior in Chrome Apps unless the
<code>app.window.fullscreen.overrideEsc</code>
permission is used to enable the app to call
<code>preventDefault</code> on keydown and keyup events.</li>
</ul>
</li>
{{/is_apps}}
......@@ -65,6 +70,8 @@ E.g. window.open(someUrl). --></dd>
<li>In Chrome Apps, pointer lock is entered without
requiring a user gesture,
prompting the user, or providing exit instructions.
Pointer lock requires the <code>pointerlock</code>
permission in the manifest.
Also, there is no default exit behavior. In normal webpages,
the browser intercepts the ESC key to exit pointer lock.
This behavior is not present in Chrome Apps.</li>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment