v134 · capabilities (fugu)

User Navigation Capturing on Desktop

Web links now direct users to installed web apps. This aligns with users' installed app expectations. Chrome makes it easier to move between the browser and installed web apps. Clicking a link that could be handled by an installed web app with the launch_handler field specified, the link will open in that installed web app, following the launch handling beha

concepts

  1. Nav Capture on Desktop

    Installed web apps can capture cross-origin navigations into the installed window on desktop. Matches the mobile behaviour.

  2. launch_handler modes

    The two named cases: chat PWA that focuses its existing window vs. editor that opens fresh windows. Pick a client_mode, fire links, watch the desktop respond.

  3. Manifest Simulator

    Dial capture_links + client_mode + scope; six real-world link scenarios show what would happen for each combination.

  4. Link Capture Tester

    Configure a PWA manifest scope, capture_links, and launch_handler.client_mode then test a list of URLs to see which would be captured by the app vs. opened in the browser tab.

why it shipped

Users expect that links to installed experiences will open in that installed experience. This is the case for native apps on all platforms and installed web apps on Android. There is a slightly broken disabled-by-default version of this on ChromeOS. This functionality has not yet been implemented on Windows, Mac, or Linux for installed web applications.

references