Re: [csswg-drafts] [css-viewport-1] [all?] Figure out if / how we want to integrate with webdriver and other similar specs. (#11282)

The CSS Working Group just discussed `[css-viewport-1] [all?] Figure out if / how we want to integrate with webdriver and other similar specs.`, and agreed to the following:

* `RESOLVED: WebDriver extensions for CSS features go into the corresponding CSS spec, in an appendix.`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> alexis_menard: issue came up when working on viewport-segment and the segments JS property<br>
&lt;TabAtkins> alexis_menard: issue was, how do we test this?<br>
&lt;TabAtkins> alexis_menard: the feature is dependent on hardware<br>
&lt;TabAtkins> alexis_menard: we usually use webdriver and emulate the hardware<br>
&lt;TabAtkins> alexis_menard: here, i needed webdriver extensions to simulate screen topology<br>
&lt;TabAtkins> alexis_menard: i have a PR to add these extensions<br>
&lt;TabAtkins> alexis_menard: got reviewed by the webdriver people, they were happy with the change<br>
&lt;TabAtkins> alexis_menard: but question is, where to put them?<br>
&lt;TabAtkins> alexis_menard: seems CSS has never put webdriver details into specs<br>
&lt;TabAtkins> alexis_menard: Looks like there's no official guidance anywhere<br>
&lt;TabAtkins> alexis_menard: some specs like posture, webbluetooth, etc all define webdriver in their spec<br>
&lt;TabAtkins> alexis_menard: webusb define in a separate spec<br>
&lt;TabAtkins> alexis_menard: webxr defines in an explainer<br>
&lt;TabAtkins> alexis_menard: so we thought it might be good to have a decision for all of css<br>
&lt;TabAtkins> alexis_menard: more cases will arrive in the future<br>
&lt;TabAtkins> alexis_menard: so where do we put the extensions?<br>
&lt;TabAtkins> q+<br>
&lt;TabAtkins> TabAtkins: Yeah let's jsut put them in the spec, an appendix is fine<br>
&lt;bramus> +1<br>
&lt;TabAtkins> astearns: contrary opinions?<br>
&lt;kbabbitt> sgtm<br>
&lt;TabAtkins> astearns: so proposed resolution is allow webdriver extensions in our specs, in appendixes.<br>
&lt;TabAtkins> RESOLVED: WebDriver extensions for CSS features go into the corresponding CSS spec, in an appendix.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11282#issuecomment-2622711531 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 January 2025 19:57:39 UTC