@b1tr0t @stefanvermaas @jaffathecake To be quite honest, from my point of view, this sounds like something that should be controllable with a simple attribute (like a new `target=”_browser”` or something similar in the same vein).
RT @tomayac: There is great information on converting existing Web Extensions to @webkit 🧠Safari App Extensions or creating new Safari App…
@stefanvermaas @jaffathecake It does. Just responded with next steps while you were tweeting. I’ll star the bug to be notified of changes myself.
@stefanvermaas @jaffathecake I see, thanks for the background.
The only way to _not_ open in a CCT currently is to link to a URL consumed by a native app (like YouTube) or to another installed standalone/fullscreen PWA.
Might be worth outlining on this bu
@stefanvermaas @jaffathecake So, the current behavior to always open in CCT was implemented in https://t.co/6ADejVKO5K. This includes all known methods (and hacks) of opening links (test app: https://t.co/Ak9qWlBc9G). I was asking to better understand the
@jaffathecake @stefanvermaas Would you have a link to the PWA in question and instructions how to navigate within this app to the link you want to open in a new window?
There is great information on converting existing Web Extensions to @webkit 🧠Safari App Extensions or creating new Safari App Extensions from scratch, but no guide on how to submit and distribute them via Xcode. Until now: https://t.co/nPSRaLV0FO. Tha
@diekus @yoavweiss The link crbug.com/new (or new.crbug.com) is a reasonable template pre-filled based on your current browser. Use it whenever you want to submit a bug for something you’re experiencing right now.