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

There's a tester app, courtesy of @alancutter, that you can play with: https://hill-glitter-tree.glitch.me/. 

Testing on a Mac (well noting that other OS may behave differently), the following options triggered from the installed PWA open in a new browser tab (nomenclature as per Alan's demo):

- `target="_blank"`
- `target="name"`
- `window.open(url, "target=_blank")`
- `window.open("about:blank", "target=_blank")` → URL

The [Launch Handler API](https://web.dev/launch-handler/), which would let you control, for example, that there only ever be just one PWA instance, is still WIP, and, as far as I can tell from my experiments, only works in an origin trial on ChromeOS. The bug https://crbug.com/1231886 shows a number of Windows/Mac/Linux "blocked-on" sub bugs.

There is, so far, no API that could express "open `<URL>` in `<this tab | that tab | a new tab | a new window | a new popup window | the browser | the OS>`", as was pointed out by Alan in an internal thread.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/989#issuecomment-1429652219

You are receiving this because you are subscribed to this thread.

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

Received on Tuesday, 14 February 2023 12:14:58 UTC