Re: [w3c/manifest] scope_extensions unreasonably prevents installation of multiple PWAs (Issue #1209)

mkruisselbrink left a comment (w3c/manifest#1209)

In Chrome the primary reason we don't show the installation prompt when you're "in scope" for an already installed app is because we don't want to show both a "open in app" and "install app" prompt at the same time. So with that in mind, would another possible solution be having a way to declare which URLs should actually be "captured" by the app? I.e. to distinguish "this URL is in scope/should not show a out-of-scope banner" from "navigations to this URL should be considered navigations to this app and launch the app or give the option to launch the app". We've had other requests for something like that as well, and it seems like that is essentially your problem/request as well.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1209#issuecomment-4076435454
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1209/4076435454@github.com>