- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Apr 2025 13:21:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-color-adjust-1] Forced Colors Mode Webdriver Emulation`, and agreed to the following: * `RESOLVED: Accept the PR, check with webdriver folks for approval` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> alisonmaher: this proposal is to add a new webdriver extension that keeps track of forced-color-mode emulation state, proposed light/dark<br> <TabAtkins> alisonmaher: it forces forced-color-mode if it's not none, and update the ysstem color mappings<br> <TabAtkins> alisonmaher: so it's a consistent experience across browsers<br> <TabAtkins> alisonmaher: put up a PR, using windows colors currently but we can do whatever<br> <TabAtkins> alisonmaher: so do we want to pursue? and not sure about process, if we need webdriver approval or just css<br> <TabAtkins> astearns: any webdriver already in?<br> <TabAtkins> alisonmaher: none in yet, but the multi-screen stuff has a proposal. i think this'll be the first.<br> <TabAtkins> astearns: anyone know how the webdriver folks like to have proposals put together?<br> <TabAtkins> alisonmaher: not sure. i looked at other webdriver specs, seemed better to put it in the sepc itself<br> <TabAtkins> alisonmaher: we can check<br> <bramus> https://drafts.csswg.org/css-viewport/#automation is the webdriver part for viewports<br> <kbabbitt> TabAtkins: we took a resolution to put webdriver stuff in our specs a while back<br> <astearns> ack fantasai<br> <kbabbitt> ...suggest we go with this for now and then check with webdriver folks<br> <TabAtkins> fantasai: tangential - how are we planning to test the final hookups to ensure it's working?<br> <TabAtkins> alisonmaher: when we test this we make the call to set one of the emulation states<br> <TabAtkins> alisonmaher: so the expectation would test the emulation's forced colors<br> <TabAtkins> alisonmaher: so we coudl use none to check it's not applied, then verify non-none works with different colors<br> <TabAtkins> fantasai: slightly different question acutally. we're gonna test this emulation, we can tell things are working as expected.<br> <TabAtkins> fantasai: but if you have a browser that supports teh webdriver emulation but doesn't acutally support asking the OS about the light/dark status, they should presumably fail *something*<br> <TabAtkins> alisonmaher: suppose could be thru the media query<br> <TabAtkins> fantasai: how do we test the MQ then?<br> <emilio> q+<br> <TabAtkins> astearns: your question is valid, but there's nothing in WPT that lets us close that final gap. it'll have to be something in the browser's own infrastructure that'll verify it work<br> <TabAtkins> fantasai: yeah my point is just that we should have some form of test that'll verify this<br> <TabAtkins> florian: as much as we like automated tests, i think there are some things that are impractical to test, and this might be one of them<br> <astearns> ack emilio<br> <TabAtkins> emilio: similar. this feels like you'd need to tweak an OS setting, assume the browser wants to pay attention to that.<br> <fantasai> Even the browser's own testing infrastructure will be an emulation layer<br> <TabAtkins> emilio: like, firefox lets you force colors regardless of the OS, that's similar to what we're using in wpt<br> <TabAtkins> emilio: so wpt can test that there's a switch and that it works correctly, but it can't test when the browser decides to trigger that<br> <TabAtkins> fantasai: yeah, that just seems to be a hole in our testing plan<br> <TabAtkins> alisonmaher: that seems to apply to testing system colors in general<br> <TabAtkins> alisonmaher: but this'll cover the rest of the space past that<br> <TabAtkins> fantasai: right, i think this is definitely an improvement.<br> <TabAtkins> fantasai: just be sure not to represent that this covers the whole space<br> <TabAtkins> astearns: so are we looking for a resolution to add this?<br> <TabAtkins> alisonmaher: yes, and i can do the extra work to double check with the webdriver folks<br> <TabAtkins> astearns: and would be easier with a spec in place<br> <TabAtkins> astearns: proposed resolution is to accept the PR, and go check with webdriver folks for approval<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: Accept the PR, check with webdriver folks for approval<br> <florian> s/impractical to test, and this might be one of them/impractical to test automatically, and this might be one of them. We should still have shared tests but they'll have to involve manual steps<br> <TabAtkins> fantasai: process - forced colors is in CR, so we shoudl make edits in ED, ping webdriver, and then publish an updated CR<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11824#issuecomment-2769343959 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 April 2025 13:21:34 UTC