wiki.mozilla.org/Mobile/GeckoVi
> Self-Contained: Because GeckoView is a standalone library that you bundle with your application, you can be confident that the code you test is the code that will actually run.
Targeting a specific release of a browser engine is a serious anti-feature.
Conversation
Replying to
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
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
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
The WebView API is a stable API provided by the platform. In order to support a feature like Web Payments, integration for it would need to be added at a new API level. For a list of what's missing, see chromium.googlesource.com/chromium/src/+ and judge for yourself if it matches their claims.
Replying to
I am sometimes really confused of how mozzila works. Considering Torbrowser, as a "secure browser" is based on it and used by the ppl of need, can be a serious concern...