Update HTML5 fullscreen/pointerlock documentation re: ESC handling.

chrome/common/extensions/docs/templates/articles/api_other.html

Index: chrome/common/extensions/docs/templates/articles/api_other.html
diff --git a/chrome/common/extensions/docs/templates/articles/api_other.html b/chrome/common/extensions/docs/templates/articles/api_other.html
index c70c2c18ae85bd596a21231c32ae679bcafcb5a6..035ce9508fe0d5a938f8eaf1c264ad02966a0d9a 100644
--- a/chrome/common/extensions/docs/templates/articles/api_other.html
+++ b/chrome/common/extensions/docs/templates/articles/api_other.html
@@ -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 fullscreen 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}}