Contact emails
alanc...@chromium.org, mgi...@chromium.orgExplainer
https://github.com/WICG/sw-launch/blob/main/launch_handler.mdSpecification
None
Summary
A "launch_handler" app manifest member that enables web apps to customise their launch behaviour across all types of app launch triggers.
Example usage:
{
"name": "Example app",
"start_url": "/index.html",
"launch_handler": {
"route_to": "existing",
"navigate_existing_client": "always"
}
}
This will cause all launches of the Example app to focus an existing app window and navigate it (if it exists) instead of always launching a new app window.
Launch handler is a successor to the Declarative Link Capturing API.
Blink component
Blink>AppManifestMotivation
Web apps currently cannot control whether they're launched in a new app window or whether an existing window is reused. This feature helps support web apps that wish to remain in a single window on desktop platforms.
Initial public proposal
https://github.com/WICG/sw-launch/issues/33TAG review
None
TAG review status
PendingRisks
Interoperability and Compatibility
Low interop risk. Web apps currently operate using the "default" launch_handler behaviour where new windows are opened on desktop and existing clients are navigated on mobile. To ensure forwards compatibility the launch_handler fields will accept lists of values similar to display_override to allow sites to use new values without breaking older browser.
Gecko: No signal
WebKit: No signal
Web developers: No signals
No, this feature involves opening/navigating app windows from various OS surface centric app launch triggers.Flag name
WebAppLaunchHandler
Requires code in //chrome?
TrueTracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1231886Estimated milestones
M96
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/feature/5722383233056768