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

Thanks for taking a look! Chromium implements this with a [new content setting](https://chromestatus.com/feature/6218822004768768): chrome://settings/content/automaticFullScreen

It is blocked by default, the default setting cannot be modified, but individual origins can be allowed. There is no Permissions API integration for now [1] and there is no permission prompt that sites can trigger.

Enterprise policy can allow or block any origin by pattern. Site settings WebUI (and the page info bubble) only permits users to modify this setting for isolated-app:// origins ([Isolated Web Apps](https://chromestatus.com/feature/5146307550248960)) for now.

The setting is somewhat similar to the longstanding chrome://settings/content/popups.

[1] Chromium [will likely add Permissions API querying soon](https://groups.google.com/a/chromium.org/g/blink-dev/c/WOch5LPq9RY). Then, we can refine this method's steps to [get the current permission state](https://www.w3.org/TR/permissions/#dfn-getting-the-current-permission-state) or [request permission to use](https://www.w3.org/TR/permissions/#dfn-request-permission-to-use) that new powerful feature entry as a condition for requiring transient activation.

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

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