@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:
WebView Behavior Depends on the App Hosting It
When an app uses WebView, the developer decides:
- Whether JavaScript is enabled
- Whether file uploads are allowed
- If pop-ups are supported
- If cookies or local storage are used
- Whether external redirects are allowed
- Whether it shows loading progress, back buttons, etc.
- If links inside the WebView can open external apps or deeper WebViews
So two different apps using WebView can behave very differently.