← Back to release summary

WebAppLaunch: user activation on focus-existing launch delivery

Category
Capabilities (Fugu)
Type
No developer-visible change
Status
Proposed (Chrome Proposed)
Intent stage
None

WPT details: Web Platform Tests or other automated test description launch_handler has no WPT coverage because installing a web app is not testable in WPT. Covered by Chromium browser_tests: WebAppLaunchHandlerBrowserTest*.UserActivation (enabled fixture asserts isActive is true and window.open() returns a window; disabled fixture asserts the opposite)

Summary

Grants transient user activation to an installed web app's existing window when a launch is delivered into it through the launch_handler "focus-existing" client mode. Today the launchQueue consumer runs without activation even though the user clicked a link, shortcut, file, or share that caused the launch, so the page cannot call activation-gated APIs such as window.open() or requestFullscreen() in response. With activation granted at delivery, apps that use focus-existing to avoid duplicate windows can still open a separate window when the launched URL belongs to a different document or workspace, in the same way a click on a Notification created by the page already activates that page.

Motivation

launch_handler "focus-existing" routes every launch into the most recently used app window and delivers LaunchParams with no user activation, so the launchQueue consumer cannot open a window for a launch that belongs to a different document or workspace, nor call other activation-gated APIs. Each launch is one user action outside the app. Precedent: a click on a Notification created by the page activates that page; notificationclick grants a service worker window interaction. Developer report: https://github.com/WICG/manifest-incubations/issues/141

Standards & signals

Ecosystem

Explainers: https://github.com/WICG/web-app-launch/blob/main/launch_handler.md

View on chromestatus.com