Why can't the browser just do the "fullscreen in a window" behaviour until/if the user approves?
No need for new events even, although a "fullscreen lost", sourced eg. from some browser UI or loss of focus, might be useful. I don't see why it would make a difference from the page's perspective whether it would was actually taking up an entire screen or just all of a certain window/tab. If the user wants the fullscreen ui without actually being fullscreen, why stop them or allow pages to force them? On 12 May 2011 18:42, timeless <[email protected]> wrote: > On Thu, May 12, 2011 at 11:12 AM, Jer Noble <[email protected]> wrote: > > Okay, here's another proposal that should work with Firefox's passive > permission system: > > > > Proposal: > > > > - Add a new boolean Element property "canRequestFullScreen". This would > map to Firefox's "Never" permission choice. > > - Add the "fullscreendenied" event. This would map to Firefox's "Not > now" permission choice. > > Your proposal makes it fairly easy for sites to stick up annoying full > content blocking "you must change your settings to proceed" elements. > > This is the wrong path. > -- -- James May
