Import WebDriver BiDi data

[caugner]

Summary

Imports support data for WebDriver BiDi under webdriver.bidi.

Bundled changes:

• Adds property implements_webdriver_bidi to browser schema.
• Uses the property to restrict the data to Chrome/Edge/Firefox/Safari.

Test results and supporting details

The data was extracted using Google Apps Script on a Google Spreadsheet used by WebDriver BiDi folks to track implementation status.

Related issues

Fixes #20207.

[queengooborg]

Nit: can we use "accepts_webdriver_bidi" to match "accepts_webextensions"?

[caugner]

How about a has array enum field that supports values flags, webextension and webdriver-bidi?

[caugner]

@queengooborg I opened #25825 to merge the accepts_* fields into an accepts array field.

[whimboo]

@OrKoN for the initial import of the WebDriver BiDi it would be great to also have the version information for Chrome. Would one of you have the time to update the implementation status spreadsheet with the information? That should be faster than having to manually edit later on. Thanks!

[OrKoN]

@OrKoN for the initial import of the WebDriver BiDi it would be great to also have the version information for Chrome. Would one of you have the time to update the implementation status spreadsheet with the information? That should be faster than having to manually edit later on. Thanks!

Hi Henrik, thanks for the ping. We could update it by the end of next week, would it be possible to delay landing the data until then?

[sadym-chromium]

@OrKoN for the initial import of the WebDriver BiDi it would be great to also have the version information for Chrome. Would one of you have the time to update the implementation status spreadsheet with the information? That should be faster than having to manually edit later on. Thanks!

I updated the features' status and started adding versions, but I wonder if the versions are actually needed?

[whimboo]

I updated the features' status and started adding versions, but I wonder if the versions are actually needed?

Thank you @sadym-chromium. Yes, the versions that we at least would need are for the initial support of a feature. For individual parameters we do not want to track the version (as what I got from Claas).

[sadym-chromium]

I updated the features' status and started adding versions, but I wonder if the versions are actually needed?

Thank you @sadym-chromium. Yes, the versions that we at least would need are for the initial support of a feature. For individual parameters we do not want to track the version (as what I got from Claas).

done

[whimboo]

Thank you @sadym-chromium. Yes, the versions that we at least would need are for the initial support of a feature. For individual parameters we do not want to track the version (as what I got from Claas).

done

Thanks! I also have to correct myself. There are actually thoughts to also include the version when parameters were added, (changed?) and removed. It's actually targeted for a later milestone, but if we want we could already start adding it as well.