Intent to Prototype: Web app launch handler

172 visualizações
Pular para a primeira mensagem não lida

Alan Cutter

não lida,
4 de ago. de 2021, 12:35:0404/08/2021
para blink-dev

Contact emails





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



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

TAG review


TAG review status



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

Is this feature fully tested by web-platform-tests?

No, this feature involves opening/navigating app windows from various OS surface centric app launch triggers.

Flag name


Requires code in //chrome?


Tracking bug

Estimated milestones


Link to entry on the Chrome Platform Status

This intent message was generated by Chrome Platform Status.
Responder a todos
Responder ao autor
0 nova mensagem