1,295
edits
Gecko:FullScreenAPI: Difference between revisions
Jump to navigation
Jump to search
→Proposed Specification
(add issues: avoiding ancestory reflow, avoiding drawing anything else) |
|||
| Line 47: | Line 47: | ||
New methods of Element: | New methods of Element: | ||
* void | * void requestFullScreenWithKeys() | ||
The current fullscreen element for the document is set to this element. | The current fullscreen element for the document is set to this element. | ||
| Line 53: | Line 53: | ||
Typically the user agent would react by transitioning the Document to the fullscreen state, or by presenting asynchronous confirmation UI and transitioning to the fullscreen state if/when the user responds affirmatively. However, the user agent is not required to do anything at all in response to requestFullScreen. The user agent's behavior is allowed to vary depending on whether requestFullScreen is called during a user event (e.g. a mouse click handler). | Typically the user agent would react by transitioning the Document to the fullscreen state, or by presenting asynchronous confirmation UI and transitioning to the fullscreen state if/when the user responds affirmatively. However, the user agent is not required to do anything at all in response to requestFullScreen. The user agent's behavior is allowed to vary depending on whether requestFullScreen is called during a user event (e.g. a mouse click handler). | ||
* void | * void requestFullScreen() | ||
As | As requestFullScreenWithKeys, but hints to the UA that while in fullscreen state, the toplevel browsing context for this Document should have keys disabled. While keys are disabled, there may be a reduced risk of spoofing attacks inducing the user to input inappropriate data, and the UA may choose to relax restrictions on entering fullscreen state with keys disabled. | ||
New DOM attribute of Document: | New DOM attribute of Document: | ||