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)

> The fact that we needed to add this behavior to force-color-adjust by default is kind of telling, IMO (https://github.com/w3c/csswg-drafts/issues/6310), and as @alisonmaher says the use-cases for this for forced colors can be achieved in other ways if necessary.

@emilio My comment in https://github.com/w3c/csswg-drafts/issues/6310 was referring to the fact that authors can currently achieve the results they want by setting `forced-color-adjust: auto` for SVG icons given that things happen at used value time. However, I do think that moving to computed value time will give authors more limited options in achieving the results they want.

Here's an example that I found while searching around: https://codepen.io/AmeliaBR/pen/xxJBgp. In this example, Chromium and Gecko produce different results due to the difference in inheritance (see screenshots below). I think Chromium's behavior is more likely to be what an author would expect in this case. Would an author have an option to get this case working in Gecko without re-declaring the original (non-forced) styles that would have been inherited previously?

### Chromium's behavior (used value time):
![chromium](https://user-images.githubusercontent.com/43683110/162787199-f5b1c96b-4838-4bd8-bcf6-4b14713991ef.JPG)
### Gecko's behavior (computed value time):
![gecko](https://user-images.githubusercontent.com/43683110/162787028-f64edead-eecb-4998-bc03-b1b5bd39ef1b.JPG)

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


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

Received on Monday, 11 April 2022 16:33:37 UTC