this post was submitted on 08 Aug 2023
1006 points (89.6% liked)
Technology
59590 readers
5882 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That is incorrect.
Firefox on Android uses GeckoView, which is a reusable Android library that wraps Mozilla’s Gecko browser engine. GeckoView is similar to WebView in some ways, but it has its own APIs and is not a drop-in replacement. GeckoView is full-featured, self-contained, and standards compliant.
Cool, totally missed that. But the issue of running both still applies right? Double the code. Viewing a site in a app it will use the chrome one ? " Google does not allow a third party to implement the System WebView and the GeckoView API is not compatible with the WebView API in a very meaningful way unfortunately, so this is not possible. "
https://github.com/mozilla/geckoview/issues/167
Viewing websites in Firefox for Android will use GeckoView and GeckoView only.
Android System WebView is only involved when other applications (not Firefox) calls the WebView API to display web pages. (e.g. when a Lemmy app opens an external link without launching a browser).
Exactly. So using both
What's the problem with using both?