3 ms·
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.
by vog 15y ago
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.
- trafficlight 15y agoI've been working on a digital signage project and I'm using Chrome's fullscreen kiosk mode for the actual presentation.
- eCa 15y ago> 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.
- tommi 15y ago> Also, F11-fullscreen doesn't stretch elements as this does Which begs the question, why not?
- tbassetto 15y agoF11-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.).
- firefoxman1 15y agoAnother 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.