Re:Full-screen API available in Firefox nightly
by vog on Monday November 14, 2011 @12:13PM
(#3234755)
What's wrong with asking the user to press F11? After all, the browser should be under the control of the user, instead of the other way around.
[ Parent
| on HN ]
Re:Full-screen API available in Firefox nightly
by eCa on Monday November 14, 2011 @12:49PM
(#3234894)
> A Web application can’t arbitrarily make an element fullscreen without user intervention—the operation has to be initiated by a user action.
As the article says, the intent is mostly to offer similar functionality as e.g. Youtube's fullscreen mode. It's much simpler/cleaner to ask ordinary users to click a button on the screen (that is a part of your own interface) than to ask them to press F11. Also, F11-fullscreen doesn't stretch elements as this does:
> It allows Web applications to toggle the browser into full-screen mode and stretch a single page element so that it fills the user’s display.
Re:Full-screen API available in Firefox nightly
by firefoxman1 on Monday November 14, 2011 @02:19PM
(#3235259)
Another reason might be that some browsers, for example the Firefox I'm running right now on linux, don't go into 100% fullscreen like chrome does. In my browser, it just removes all of the browser's interface except the URL bar and tabs.
Re:Full-screen API available in Firefox nightly
by tommi on Monday November 14, 2011 @12:58PM
(#3234926)
> Also, F11-fullscreen doesn't stretch elements as this does
Which begs the question, why not?
Re:Full-screen API available in Firefox nightly
by tbassetto on Monday November 14, 2011 @01:02PM
(#3234951)
F11-fullscreen stretches the browser window.
Using the fullscreen API, you can put in fullscreen some specific parts of your website (a specific div, a specific menu, etc.).
Re:Full-screen API available in Firefox nightly
by trafficlight on Monday November 14, 2011 @12:17PM
(#3234766)
I've been working on a digital signage project and I'm using Chrome's fullscreen kiosk mode for the actual presentation.