Re: [w3c/manifest] Standardize when link clicks or navigations enter and/or leave installed PWAs (#989)

dmurph left a comment (w3c/manifest#989)

So there are two issues here:

1. The original issue is that, if you installed the 'paypal' websites as a PWA, on Android we capture ALL url clicks or navigations (no matter what the target or relationship is - e.g. auxiliary frames get intercepted, same-site navigations intercepted, etc) into the installed pwa if the url is in-scope. This breaks a bunch of stuff, especially if it's something like paypal which relies on opening child frames to, say, paypal logins.
2. There is another issue of navigations IN a pwa opening in a custom tab, even if it's supposed to be target=_blank / new browser context.

I have renamed this issue to `Standardize when link clicks or navigations enter and/or leave installed PWAs` to hopefully make this more clear.



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

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