[go: up one dir, main page]

Skip to content
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

Add WebView Browser support for various OS #6167

Open
mr-roadl opened this issue Feb 5, 2022 · 5 comments
Open

Add WebView Browser support for various OS #6167

mr-roadl opened this issue Feb 5, 2022 · 5 comments

Comments

@mr-roadl
Copy link
mr-roadl commented Feb 5, 2022

More and more web developers nowadays are going to build desktop apps with the web techstack. It would be really handy to see supported Web APIs inbetween the different WebViews, talking WKWebView for MacOS, IWebBrowser2 and WebViewControl for WIN, WebKitWebView for Linux and so on

@LifeIsStrange
Copy link
LifeIsStrange commented Feb 5, 2022

Who is gonna fill the data manually for all those webviews? Seems like a lot of human resources for what is a massive duplication.
The default webview of an OS always resolve to the default browser of the OS (webkit for Ithings), chromium Edge for Windows products.

Sure there can be minor differences between what a webview allow and what the default browser allow, this is at least the case on Android. I had found a way at the time to find all the missing features on android webview vs chrome browser (don't remember how) and the list was ridiculously small, like ~5 features among thousands where missing vs chrome, and among those 5 ~3 made sense to avoid because they were irrelevant for web views. Among the other 2, I commented on chromium tickets and progress has been made in recent years regarding parity.

What i mean is: what matters is to show the difference between a webview and its respective browser by showing its very few missing features/behavioral differences and its additional features (probably none)
Such an UX might need a special dedicated page on caniuse.

@mr-roadl
Copy link
Author
mr-roadl commented Feb 5, 2022

@LifeIsStrange

What i mean is: what matters is to show the difference between a webview and its respective browser by showing its very few missing features/behavioral differences and its additional features (probably none)
Such an UX might need a special dedicated page on caniuse.

Yeah, that is probably a really good suggestion.

@LifeIsStrange
Copy link

A notable missing feature is the web payment APIs
https://chromestatus.com/feature/5639348045217792
(as you can see the platform webview is missing)

@LifeIsStrange
Copy link

So I have found a way to find the exhaustive difference:
On the search bar of chromestatus.com
Type browsers.chrome.webview<98
It will list all features since version 0 to 98
Then type the other similar search query for Chrome Android (non webview)

Then apply a dom selector on the console to count the total number, substract them and you got the total diff number.
An elaborate selector could filter the elements that differ.

@romainmenke
Copy link

There has been some movement on this in mdn browser compat data.

Relevant links:

Can the mdn data be used to add support for these in caniuse?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants