[css-viewport-1] [all?] Figure out if / how we want to integrate with webdriver and other similar specs.

[emilio]

In #11137 we have a PR for adding webdriver integration to one of our specs.

As far as I can tell there's no precedent for that so it's unclear whether that (just stash that in the CSS specs) is the right way to go.

Much like segments, media queries and other things might benefit from this.

So I'd like to agree on how to do this kind of stuff for all CSS specs. Should we:

• Stash them in the relevant spec.
• Put them somewhere specific (some automation spec?)
• Don't.

What do people thing? @fantasai @tabatkins

[darktears]

Adding again my comment from the original PR since it could be relevant to the discussion.

WebAuth, Device Posture, Compute Pressure, Generic Sensors, Web Bluetooth for example define the automation/testing story in their respective main specs.

Some specs like WebUSB are defining them into a dedicated spec, some specs into an explainer like WebXR.

So, I don't think there is a W3C guidance around that however there is a guidance around landing WPT tests, and many specs or features do need hooks in WebDriver.

I think the WebDriver folks have said that they want to keep the WebDriver spec to specify the core aspect of WebDriver not every hook from every specs. Also let's be honest it's better to specify these hooks as close as possible from the feature so that if the feature is extended/modified it's likely that authors will also update the testing aspect of it.