@tobi It was me. I wrote about this- BUT WebView is NOT A BROWSER & that could be the problem. It has to be triggered by an app & its behavior is dictated by a specific app.
@haleme , like I mentioned above:
WebView is not a full browser.
It’s a tool that apps can use to show limited web content inside the app itself.
If there is no dedicated browser installed, and no system-level handling for general links, WebView alone cannot just “open links” from anywhere like SMS messages.
In a traditional smartphone SMS app, when you tap a link, the system usually needs to hand off the link to a browser app because that’s the job of a full browser.
Kompakt’s SMS app does …
@zoltan & @kirkmahoneyphd I believe this is the SIDELOADED app that’s triggering this functionality.
Basically: Different apps = different WebView capabilities, based on what the developer wants to allow.
Different apps can trigger different behaviors and permissions within WebView, because WebView is essentially a blank slate that app developers can customize based on what they allow or restrict.
Users sideloading apps need to understand that:
1 Like