-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No "native" Chrome in Experimental #12
Comments
I'm not sure. This may be a bug in the v1.1 release. In other words, chrome should not be displayed. |
I don't know actually. Just explaining what I expect to see - and what I see. Actually "Chrome" is mentioned even on your screenshots ))) If it is a bug - you'd better remove it from there to avoid misunderstanding. |
It should not be simply removed, as some versions of Chrome should be displayed on some Android versions. This involves complex historical legacy issues in webview. |
I think your module has given users a misunderstanding. |
Other applications work fine with Chrome's webview on AnyWebView version 1.1. I simply won't use your repository anymore, that's all. If you don't want to solve the issues, it's your choice. |
You may be talking about custom tabs, Try an app that actually use webview, like https://play.google.com/store/apps/details?id=mark.via.gp |
It won't launch for me |
Hi! Developers of WebView Manager here, a different approach to what AnyWebView does. Like mentioned above, chrome on 10+ cannot function as a WebView. In fact, chrome on those Android versions completely ships without the WebView components due to the new "Trichrome library". Without getting too complicated, there are three apps, chrome, WebView, and shared code (the actual Trichrome library). All three have to be present, and only the WebView component can function as a WebView now. AnyWebView might let you select chrome but that doesn't mean it'll work, unfortunately. Apps access WebView via the AndroidX WebView library. We don't actually interact with lower level parts of WebView, so we can't "fix" an issue that is created by using an invalid WebView provider. Hope this clears things up! |
Just for your information, I have two applications that developers added support for Chrome's webview upon my request. So it is possible. However, if you choose not to do so, it is entirely your decision. I just provided this information for general knowledge. |
Assuming they didn't just start using custom tabs or aren't somehow overriding the system default WebView to use actual webview, and actually somehow got chrome to function as a WebView when it's entirely missing the WebView library on A10+, that would still be a custom adaptation every single app would have to do. Quite the task, for an extremely small amount of users. |
Good proposal. |
v1.2 "experimental" does not show "Chrome" (I mean native Chrome, not Android System Wevbview) in webview settings while v1.1 does.
Not too critical but whatever.
If any additional information is necessary - let me know what you need.
The text was updated successfully, but these errors were encountered: