Re: [csswg-drafts] [css-color] [css-color-adjust] Make system colors fully resolve (but flag they were system colors) thus reversing the resolution of #3847 (#6773)

I have been discussing this issue with @smfr, and WebKit believes that system colors should resolve at used-value time, after inheritance. Our reasoning is as follows:

* The existence of a `color-scheme` boundary implies authors want to further customize the appearance of their content. We would expect authors to test accordingly and observe the consequences of intentional `color-scheme` changes, limiting the occurrence of legibility issues.
* Form controls already change their appearance across `color-scheme` boundaries, without any other author style changes. Authors may expect system colors to match form controls. In this scenario, we believe that authors should not need to redeclare `color` in order to match the current `color-scheme`.
* We agree with @fantasai's benefits of resolving at use-value time: [#4915 (comment)](https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-701674628) (https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-701674628) and [#4915 (comment)](https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-707969753) (https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-707969753).
* Finally, we consider `color-scheme` boundary changes to be a rare use case. Additional data is needed to back this claim.

-- 
GitHub Notification of comment by pxlcoder
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1075459585 using your GitHub account


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

Received on Tuesday, 22 March 2022 18:11:16 UTC