← Back to release summary

Automatic Fullscreen Content Setting

Category
Capabilities (Fugu)
Type
New or changed feature
Status
Enabled by default (Chrome 127)
Intent stage
None

Summary

A new "Automatic Fullscreen" content setting permits Element.requestFullscreen() without a user gesture, and permits browser dialogs to appear without exiting fullscreen. The setting is blocked by default. Sites can query for permission (starting in M128), but cannot prompt. New UI controls are limited to Chrome's settings pages [1] and the site info bubble. Users can allow Isolated Web Apps [2], and enterprise admins can allow additional origins with the AutomaticFullscreenAllowedForUrls policy. Combined with Window Management permission [3] and unblocked popups [4], this unlocks valuable fullscreen capabilities: - Open a fullscreen popup on another display, from one gesture - Show fullscreen content on multiple displays from one gesture - Show fullscreen content on a new display, when it's connected - Swap fullscreen windows between displays with one gesture - Show fullscreen content after user gesture expiry or consumption [1] chrome://settings/content/automaticFullScreen and site details pages [2] User control is initially scoped to security-sensitive apps; see https://chromestatus.com/feature/5146307550248960 [3] For multi-screen window placement features; see https://chromestatus.com/feature/5252960583942144 [4] To similarly permit window.open() without a user gesture; see chrome://settings/content/popups

Motivation

Some web apps (e.g. finance, gaming, point-of-sale, signage, and presentation) require multi-screen fullscreen from one gesture. Virtual Desktop Infrastructure (VDI) clients also require fullscreen without a gesture to: - Automatically extend a fullscreen desktop session onto a newly connected display - Request fullscreen after transient activation expiry, e.g. slow remote host response - Request fullscreen after transient activation consumption, e.g. auth interstitial on connect - Apply remote app fullscreen state locally, e.g. on app launch or system events - Restore fullscreen on local display changes, local user session unlocks, other local OS Window Manager interruptions

Standards & signals

Docs: https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture

Samples: https://github.com/michaelwasserman/iwa-windowing-example

Explainers: https://github.com/explainers-by-googlers/html-fullscreen-without-a-gesture

View on chromestatus.com