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

@a-type wrote:
> A link in a PWA with rel="noopener" and/or target="_blank" will open in another app - be it browser or other app registered to handle the link, like another PWA

I believe target="_blank" implies 'noopener' now in anchor links, but sadly not in `window.open`, which requires 'noopener' to be specified manually.

Those link clicks would be 'capturable'.  If there is an app that controls that url, then it could be opened in that app. If not, then it would be opened in the browser.

@a-type wrote:
> A link in a PWA with rel="opener" will (may?) open inside the PWA as a frame overlay.

This would open in whatever context the navigating-from browser context is in. If we are in an app, we open an app window for that, as it's in the same browser context group. If we're in the browser, we open in browser tab. (assuming we're creating a new browser context - if that target is a named frame that exists or self, then it would never be capturable.

I think we also want to special-case a middle-click on desktop that this is capturable but we force the 'new-client' behavior of launch handling, and we perhaps force the same context (of app or browser). So we still go in the launch queue but we ensure the expected user behavior of opening a new thing.


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

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