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

• a compelling downstream-consumer story (e.g., MDN or caniuse express an interest, or someone is planning to do something with the data that might plausibly grow BCD's reach)

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.

• reviewers (e.g., two or more people with interest and ability to test data relating to new and existing releases, or at least one reviewer acting on behalf of the vendor)

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.

• a release process allowing BCD to publish stable release information in a browsers/ file (containing release notes with version numbers and dates)

Does WKWebView have recordable version numbers and a release process?

• documentation (e.g., how to get and test a feature in that browser, links to resources that might help with it, etc.)

Does the vendor provide release notes etc.?

Can we run WKWebView in Selenium? Ideally it would be integrated in compat data collection offered by the @openwebdocs mdn-bcd-collector project.

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.

• a release process allowing BCD to publish stable release information in a browsers/ file (containing release notes with version numbers and dates)

Does WKWebView have recordable version numbers and a release process?

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.

• documentation (e.g., how to get and test a feature in that browser, links to resources that might help with it, etc.)

Does the vendor provide release notes etc.?

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.