[whatwg] api for fullscreen()

[David Singer]

On Feb 4, 2010, at 16:53 , Kit Grose wrote:
> I also develop kiosk and medical applications where fullscreen is not only desirable but necessary behaviour. Crippling the API such that the developer cannot determine whether or not the user permitted their application to run fullscreen is unnecessary—it's up to developers to use the API in a usable manner, and up to UAs to provide an easy "escape hatch" if the developer fails to do so, just like in desktop environments.


You're not crippled in this environment.  In a kiosk, you write the content, choose your browser, OS and hardware platform.  You can (and maybe should) use non-standard extensions to take a vice-like grip of the display and UI.

David Singer
Multimedia and Software Standards, Apple Inc.