- From: Glenn Maynard <glenn@zewt.org>
- Date: Tue, 8 Feb 2011 17:04:58 -0500
- To: João Eiras <joao.eiras@gmail.com>
- Cc: public-webapps <public-webapps@w3.org>
Received on Tuesday, 8 February 2011 22:05:31 UTC
On Tue, Feb 8, 2011 at 3:12 PM, João Eiras <joao.eiras@gmail.com> wrote: > >> Regarding the web page requesting full screen access, I regard it as > >> dangerous, disruptive and unnecessary. > It's only dangerous or disruptive if implemented carelessly. It's simply false to claim it's unnecessary. - Video players must be able to go fullscreen when the video is double-clicked; that's a fundamental UI. - I shouldn't have to manually fullscreen a game every time I load it. - Browser fullscreening doesn't allow you to determine which element is being brought fullscreen, if there's more than one candidate. - There are many other interesting use cases which browser controls don't address at all; for example, native image viewers often show thumbnails and only go fullscreen when an image is selected. -- Glenn Maynard
Received on Tuesday, 8 February 2011 22:05:31 UTC