Re: [whatwg/fullscreen] Enable configuration for fullscreen without transient activation (PR #235)

To more concretely answer your questions, as they pertain to Chromium's current implementation:
> Is it a command line flag or similar that would be enabled in kiosk mode and thus unchanging for the duration of a browsing session, or does it depend on the use of other features like the Window Management API?

No, Chromium's per-origin setting values can change during a browsing session, are not specific to kiosk or any other mode, and does not depend on the Window Management API.

> The direction of my question is whether we should have UA-defined state that we look at here, or if it really is "configured to permit fullscreen without transient activation" in a global sense.

The UA defined state in Chromium is a per-profile, per-origin content setting.

Additionally: We could codify in spec that Chromium implements an initial usable security mitigation for this feature: Origins allowed to use Automatic Fullscreen will still [require transient activation shortly after a same-origin WebContents exit](https://crsrc.org/c/content/browser/web_contents/web_contents_impl.cc;drc=f0e48627a874a75ff702a7c5aaf90b9dc33a6119;l=10247)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/235#issuecomment-2115879452
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/pull/235/c2115879452@github.com>