Contact emailsmgi...@chromium.org, alanc...@chromium.org, c...@chromium.org
New Web App Manifest members to control what happens when the user navigates to a page within scope of an installed web app.
This feature introduces the "capture_links" member, an enumeration allowing the customization of link capturing behaviour, allowing sites to:
- Automatically open a new PWA window when the user clicks a link to their app.
- Have a "single window mode" like mobile apps.
After a user installs a PWA, currently the only way to open that PWA in its standalone window is to launch it directly from the system launcher, or use hard-to-discover Chrome menus to "pop out" web pages into the installed app.
Site developers commonly request the ability for when the user clicks a link into their (already installed) app's scope, it automatically opens the app window. This mirrors the behaviour of apps on mobile which do this automatically.
Site developers also frequently request the ability to, by default, focus an existing instance of the app rather than opening a new one. For example, a music player app doesn't make sense to open a second instance.
TAG review statusPending
Interoperability and Compatibility
Very small, since any browser not implementing this will just fall back to the standard behaviour, which is to navigate to links in a browser tab.
The design presents a forwards compatibility risk, which is that any new modes added after the initial release would not be supported on earlier browsers, forcing developers to break older browsers if they want to use newer modes (similar to what happened with "display"). We can work around this by accepting a fallback list.Gecko
: No signalWebKit
: No signalWeb developers
: No signals
Link to entry on the Chrome Platform Statushttps://www.chromestatus.com/feature/5734953453092864