Philip Jägenstedt

Thanks @michaelwasserman! The 6 use cases from the [explainer](https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture/blob/main/README.md#use-cases) and [Intent to Ship](https://groups.google.com/a/chromium.org/g/blink-dev/c/WOch5LPq9RY) fall into a few categories: > Show fullscreen remote desktop content on multiple displays with one user...

@michaelwasserman is there an open spec issue for the permission bit?

Per our [working mode](https://whatwg.org/working-mode#changes) we need interest from two implementers for normative changes. This change is a little bit different from most in that default behavior isn't changing, it's closer...

@annevk see https://github.com/whatwg/fullscreen/pull/235#issuecomment-2116881494 for my breakdown of the use cases. The last 2 about remote desktop applications seem to rule out any more targeted approach, and the "newly connected display"...

@martinthomson is it a fair summary to say you're suggesting a way to request fullscreen and keyboard lock at the same time? cc https://wicg.github.io/keyboard-lock/ editors @garykac and @jamiewalch

I tried something in https://github.com/whatwg/fullscreen/compare/fullscreen-is-prevented?expand=1 but I don't really like that either. I'll just leave it on a branch in case I want to get back to it, and close...

I think the code that makes this work in Chromium is [this](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/css/fullscreen.css;l=52-59;drc=17460926782b758f5cd86552221182bb9b188ce5): ```css :root:-webkit-full-screen-ancestor { overflow: hidden !important; } ``` `:-webkit-full-screen-document` was used previously, but changed in https://codereview.chromium.org/807473002. Specifying this...

How is the special case implemented in Firefox? Is it to skip step 4 of https://fullscreen.spec.whatwg.org/#fullscreen-an-element?

That definition was added in https://github.com/w3c/screen-orientation/pull/90 and then flip-flop-flipped out of the spec again: https://github.com/w3c/screen-orientation/commit/367e386bf365b0f660ff24c3afce2775817a6df3 https://github.com/w3c/screen-orientation/commit/597c7bf7639f65c4f6ed6d8ae3142c0a15a3498e https://github.com/w3c/screen-orientation/commit/1ab4b3d51532af851cf26feff63855262864bd04 @marcoscaceres was the definition moved to some other spec?

@marcoscaceres is this something you'd still like to pursue? Is there implementer interest?