- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Apr 2022 06:11:39 +0000
- To: public-css-archive@w3.org
> @emilio My comment in #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 forced colors to computed value time will give authors more limited options in achieving the results they want. That is true. > 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 in Forced Colors Mode 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. Is it though? If you use currentColor, you most likely want stuff to fit with the surrounding text, which is Gecko's behavior. In any case guessing author intent is hard, and you're right that forcing colors at computed value time the original author-specified colors are lost down the tree (though that's different from the question of whether system colors should themselves resolve at computed or used value time). -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1096135004 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 April 2022 06:11:42 UTC