Enable fullscreen API
See original GitHub issueIs there a way to enable the fullscreen API for the qbrt shell? i e a user loads Youtube into a qbrt shell, accesses a video, clicks the “fullscreen” button and receives a fullscreen representation of the video?
I remember back in the Xulrunner days you had to set a preference (in prefs.js
) for that.
However, that no longer seems to work. Or perhaps I’m just not remembering the correct preference (I tried setting full-screen-api.enabled
to true and full-screen-api.approval-required
to false).
Setting window.fullScreen
to true from a chrome privileged scope isn’t always an option, so enabling the requestFullscreen
API would be highly appreciated.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Fullscreen API - MDN Web Docs
The Fullscreen API defines two events which can be used to detect when fullscreen mode is turned on and off, as well as...
Read more >Using the Fullscreen API - DigitalOcean
Immerse users by taking them fullscreen! You'll see how to use the simple Fullscreen API in JavaScript to create fullscreen web experiences!
Read more >Full Screen API | Can I use... Support tables for HTML5, CSS3 ...
API for allowing content (like a video or canvas element) to take up the entire screen. Usage % of. all users, all tracked,...
Read more >Experimenting with the FullScreen API - LogRocket Blog
To enable a full-screen view on a user's browser, you will first need to ask for permission to do so with the Element....
Read more >How to Leverage the Fullscreen API… and Style It | CSS-Tricks
Let's look at the Fullscreen API in JavaScript. It allows you to do a pretty powerful thing: full screening exactly one particular element ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
qbrt copies its application files (including prefs.js) into the Firefox installation dir after it installs Firefox into the dist/ dir. If you make changes to qbrt’s app files, you need to
node ./bin/install-xulapp.js
afterward to get qbrt to re-copy those files. (Warning: that script is internal and unstable, so it’s likely to change.)Yep.
Just tried that. I can confirm that actually works. It seems the issue comes down to an implementation detail of my app (which uses
mozbrowser
for its views).Well. No biggies. I’ll fix that eventually.
Right now I’d just like to get down and dirty with some qbrt internals. Adding
require()
to my internal fork yesterday afternoon stoked a fire in me. 🐱 🐶