Conversation

The status quo is targeting a stable API without being able to depend on a specific version, since it receives automatic updates. Encouraging applications to bundle their own web rendering engine specifically so they can delay updating it is serious step backwards for security.
1
3
Not to mention to severe loss of security going from a well sandboxed rendering engine like the standard WebView to a browser engine with no sandbox implementation for the platform. The 3rd point on that list is simply dishonest, which is typical of how Mozilla presents Firefox.
1
2
Their initial claim that "many advanced Web APIs are disabled" in the WebView is misleading. A few features requiring a user interface outside of the content like Web Payments are unavailable. It still has more standards coverage than Firefox and is successfully used by browsers.
1
This Tweet was deleted by the Tweet author. Learn more
Replying to
They don't have a sandbox in their current generation browser either and I'm not saying that their new approach is a regression for their own usage. I already cover their current generation Android browser app in grapheneos.org/usage#web-brow and it applies entirely to the new one.