W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] [css-color-4] Make system color keywords compute to themselves (#3847)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 30 Oct 2019 16:22:15 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-547990842-1572452534-sysbot+gh@w3.org>
The CSS Working Group just discussed `Make system color keywords compute to themselves`, and agreed to the following:

* `RESOLVED: Make system color keywords behave like currentColor and inherit as keywords`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Make system color keywords compute to themselves<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3847<br>
&lt;dael> TabAtkins: Back in the day system colros could become rgb at computed value time. Now that we can switch user themes using color-scheme you can turn it on and off at subtree. That changes what system colors resolve to<br>
&lt;dael> TabAtkins: Thus they should act like currentColor<br>
&lt;dael> TabAtkins: Talked to our impl and it's fine<br>
&lt;dael> chris: Issue about animation, but can animate currentColor<br>
&lt;dael> AmeliaBR: Don't have interop on currentColor<br>
&lt;dael> AmeliaBR: As far as making system color keywords inherit as keywords we want them same as currentColor. We just need impl to go through details of making currentColor and these inherit as keywords<br>
&lt;dael> AmeliaBR: Right now FF does it. Chrome and I think WK do not<br>
&lt;dael> TabAtkins: Chrome appears to. I tested yesterday. We're doing it sufficiently close to look correct in a test<br>
&lt;dael> AmeliaBR: DOesn't when you animate or you're newer chromium version<br>
&lt;dael> TabAtkins: Might be jsut passin gmy straightforward test<br>
&lt;tantek> interesting, thought we had enough currentColor tests to get interop. curious about the test cases that demonstrate non-interop<br>
&lt;fantasai> dbaron, getComputedStyle would return a resolved color<br>
&lt;dael> AmeliaBR: Complexities with animations; if we still agree currentColor spec is right those same rules would apply to making system colors inherit as keywords<br>
&lt;dael> chris: Makes sense to me<br>
&lt;dael> myles: Does that mean fingerprinting is no longer necessary?<br>
&lt;dael> TabAtkins: Nope because they always show as rgb in gCS<br>
&lt;dbaron> s/fingerprinting/fingerprinting stuff we just resolved on/<br>
&lt;dael> TabAtkins: THat's hard compat requirements, people have been relying on it<br>
&lt;dael> chris: Need animation on current and system colors?<br>
&lt;dael> TabAtkins: Sure<br>
&lt;AmeliaBR> s/animation/animation tests/<br>
&lt;dael> AmeliaBR: With the cavaet that we need more tests, any obj to making system color keywords behave like currentColor and inherit as keywords?<br>
&lt;tantek> inherit as keywords makes sense to me<br>
&lt;dael> RESOLVED: Make system color keywords behave like currentColor and inherit as keywords<br>
&lt;fantasai> +1, we need this for them to behave correctly in the presence of forced-color-adjust / color-scheme<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3847#issuecomment-547990842 using your GitHub account
Received on Wednesday, 30 October 2019 16:22:17 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC