-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Consider adding WKWebView #23296
Comments
Thanks @RupertBenWiser, adding this to our meeting agenda. From our guidelines, there will be the following questions to be answered: https://github.com/mdn/browser-compat-data/blob/main/docs/data-guidelines/browsers.md#addition-of-browsers
I think this requirement is met given the use in https://caniwebview.com and the general interest to have more compat data recorded for web views.
Do you plan to act as the main contact or do you want to loop in other people? Can we run WKWebView in Selenium? Ideally it would be integrated in compat data collection offered by the @openwebdocs mdn-bcd-collector project.
Does WKWebView have recordable version numbers and a release process?
Does the vendor provide release notes etc.? |
As far as I know, this used to work but does not currently. Safari itself has WebDriver support: https://developer.apple.com/documentation/webkit/testing_with_webdriver_in_safari?language=objc But that's not useful for figuring out the state of WKWebView outside Safari.
WKWebView is released with iOS updates. Each iOS release has a distinct version of WKWebView, and there is no way to update WKWebView outside of iOS release. This means that iOS version numbers can be treated as WKWebView version numbers.
There are usually very brief notes on apple.com: https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-17_4-release-notes#WebKit Most of the time these cover all WebKit use cases, not just the non-Safari WKWebView case we are interested in here. The WebKit blog usually has a more detailed write-up (e.g., https://webkit.org/blog/15383/webkit-features-in-safari-17-5/) and will specifically call out major changes related to WKWebView. However, these will generally not answer the question of "what is not supported in WKWebView", so they are useful for learning about features that were missing in WKWebView but have now been added, but not for learning about new features that are supported in Safari but not in WKWebView. |
What type of issue is this?
Missing compatibility data
What information was incorrect, unhelpful, or incomplete?
User agents (outside of Europe) on iOS need to use WKWebView. This seems like a pretty core piece of data to track then. For full transparency, I am a co-chair for the WebView CG and we also just started displaying BCD results on caniwebview.com so it would be great to make this data more visible there.
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
My understanding is that webview_android mirrors chrome_android with adjustments. So perhaps we could have webview_ios? I'm happy to help dive into this if you think it is worth doing.
Did you test this? If so, how?
N/A
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
The text was updated successfully, but these errors were encountered: