An installed PWA (standalone) opens a target="_blank" link in the
in-app browser (Android Custom Tab). Choosing Open in Chrome from that
in-app browser's overflow menu opens the URL in Chrome but also tears down the
originating PWA:
The web app is killed and reloads its start_url, losing all
in-page state (issue 41495930). With a 3rd-party launcher it drops to home.
The web app window is finished and removed from the app overview entirely (issue 510460240).
Firefox keeps the installed web app alive in the same situation.
target="_blank" button → in-app browser opens.session id.The APK is a local org.chromium.chrome build with the fix.
Verified on a Pixel 6a (Android 16): with unfixed stable Chrome "Open in
Chrome" removes the PWA from recents; with this build the PWA task stays
alive.
"Open in Chrome" opens the URL in the main browser; the installed web app
stays alive in the background with its state and session id
intact (Firefox behaviour).
The web app is finished: a WebAPK cold-reloads its start_url
(new session id), a shortcut PWA is removed from the app
overview entirely.