Re: [whatwg/fullscreen] Allow fullscreen on initial load of a page (#36)

Yes. My team developed a HTML5 presentation editor, and the presentations try to request full screen on loading. Currently only works in Firefox when `full-screen-api.allow-trusted-requests-only` is set to `false` (we don't recommend users to set this, of cause).

We want the output presentation docs can be hosted in any site, and can be linked to from any site with minimum efforts. Fullscreening a iframe to embed the presentation could work sometimes, but has limitations:

* Need some programming on the embedding sites, instead of a simple `<a>`.
* Hard dependency on the embedded docs. What if a embedded doc is replaced in future with a doc that doesn't need full screen? The embedding page also need to inform the embedded doc when it enter/exit full screen, and the protocol (maybe via `postMessage`) is also a hard dependency.
* Users have difficulty to bookmark the embedded docs.
* Consumes more RAM, because the embedding page is still there although not visible when full screened.
* Looks strange if the embedded docs fail to load (404 etc.).

So I still think it's better to simply allow `requestFullscreen()` within `navigationStart` + N sec if the navigation is trigger by user action.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/36#issuecomment-247198262

Received on Thursday, 15 September 2016 00:30:13 UTC