TZP: fullscreen not exiting
With most configurations the fullscreen test fails cause mozfullscreenchange is never triggered (fullscreenchange is triggered though).
When I clone the git repo and open the main test through a file:// link the test works (but not with a local http server).
I might investigate further myself but I am not sure where.
OS: alpine linux Browser: FF 125, ESR 115, FF 126 dev
About this issue
- Original URL
- State: closed
- Created 2 months ago
- Comments: 17 (15 by maintainers)
Commits related to this issue
- fixup #307 — committed to arkenfox/TZP by Thorin-Oakenpants 2 months ago
- fixup #307 (#308) — committed to arkenfox/TZP by Thorin-Oakenpants 2 months ago
- tidy (#309) #307 — committed to arkenfox/TZP by Thorin-Oakenpants 2 months ago
- clarify what is being tested, #307 — committed to arkenfox/TZP by Thorin-Oakenpants 2 months ago
- use DOMRect if we can, #307 — committed to arkenfox/TZP by Thorin-Oakenpants 2 months ago
So I just cleaned up some logic, and use the same code for all platforms (but if android I exit FS element afterwards) - this has made android super speedy 😃
So you can now F11, click fullscreen element when in F11 or already in fullscreen element, etc … and resizing on desktop autohappens as well … etc … and I notate what I’m measuring. It’s not not a full screen element, then I use window.inner (Width/Height), else I measure the element (clientWidth/Height)
So I used to use a image, which AFAICT didn’t involve scrollbars. But by using document.documentElement this now reflects the viewport size, not the actual full screen - so I might look at using a transparent underlay or something - and this will allow me to use clientrect - so stay tuned, more changes to come at some stage
PS: and now it all works on any browser engine too
If I use F11 while the page is open the result is a bit inconsistent (
1302 x 828or1302 x 902) and differs from the result when reload the page while staying in fullscreen (1300 x 900).Any guess why?
full-screen-api.warning.timeout: 0andui.prefersReducedMotion: truemay have something to do with it. No time to debug further right now.For me F11 keeps letterboxing and with the button letterboxing is bypassed.