Hey PWA folks, is there a way I can prevent Chromium browsers from nesting links clicked inside a PWA into "webviews" inside the PWA? I just want my links to open in my regular old browser window, not in a frame inside the app I was using when I clicked it.
- he/him
- duriansoftware.com/
the swift programming language is my fault to some degree. mostly here to see dogs, shitpost, fix old computers, and/or talk about math and weird computer programming things. for effortposts check the #longpost pinned tag. asks are open.
email
mailto:joe@duriansoftware.com
discord
jckarter
webzone
duriansoftware.com/code stuff
github.com/jckarter/fediverse
f.duriansoftware.com/@joeYou must log in to comment.
in reply to @nyquildotorg's post:
If you mean specifically w/r/t wrapped web views on mobile, I think you need to have a native handler to do that. At least that is my memory on iOS with Ionic, which I was last knee-deep in a year ago.
What I want to do is have every link handed off to the native OS, on Android. Just because the app I'm using is already technically a browser shouldn't mean the page should open inside the app; give links to the native app that's designated to handle them. (The browser.)
Ah, I see. No idea if Android honors it but have you tried setting the scope in your PWA’s manifest? IIRC iOS didn’t always honor it consistently but I think it does now.
The issue is that I'm not building a PWA, I just use a lot of PWAs and am very tired of having to open links and then manually open them in my browser after they open in a useless tab inside the PWA
I'm just completely baffled that there wouldn't be a preference for this, and am trying to come up with a workaround that doesn't involve patching Chromium and getting my patch accepted
Oh, I see. Yeah, it's up to the folks who make the PWA to specify their own scope, and it's not something that can be easily inferred what is and is not within the scope of a PWA. It does suck, though.
I had a conversation yesterday with Alex Russell who was there for the discussions that led to this, and he essentially said that "mobile app developers want to be able to trap people in their app, and we needed app developers to build PWAs."
The real reason for corporate-led specifications is to convince people to build something with it, not so that the poor fuckers who use the products built with them have a good experience. It sucks.