Re: [w3c/manifest] Provide a way to not open a link in the PWA, in the moment (#989)

I'm realizing that the use case I'm looking for (opening the user's default browser / pwa host browser when clicking a link inside the PWA) is different from the original problem cited in this issue (opening a link in the user's browser opens the PWA because it matches the scope).

Given this issue isn't getting any attention, I wonder if it would be worth diverging these two use cases. I think some other commenters are also in my situation. Just want to keep things disambiguated.

For my problem, a few solutions come to mind:
- Just have PWAs interpret `_blank` as a link for the user's browser (probably not viable as it breaks with existing behavior)
- Add a manifest option to 'allow list' particular origins for external opening instead of in-pwa frame view
- Add a new attribute or new attribute value for anchor tags which hints to PWAs to open in the user's browser instead of in-pwa.

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

Message ID: <w3c/manifest/issues/989/2118329247@github.com>