I'd hate to browse within a desktop app that's not my browser, notably because I use an adblocker.
I'd expect the PWA to act like every other software, which means using the default tool to open links (letting the OS manage, basically).
Also, about target=_blank, a good read around security, as it could create some huge flaws.
Great point about ad blockers.
Yep, definitely adding rel="noopener noreferrer" alongside "target=_blank" though I'm not sure those same vulnerabilities would apply to PWAs. Seems like that should be somewhat of a firewall between the two. I'd be curious about whether that vulnerability persists.
It's not just adblockers, there's a lot of functionality missing, like having to log in again to something your browser normally handles or syncing your history with another device.
Critically for me, I'd miss being able to bookmark something once I find it. Everything linked to from within the fake browser is lost forever unless you take a screenshot or remember what steps you took to get there.
Sooo, I haven't checked on this for a while.
Did you test for such a vulnerability since then?
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.