- From: Alison Maher via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Feb 2022 21:35:33 +0000
- To: public-css-archive@w3.org
@tabatkins That's correct. And since I don't think this has been mentioned in the thread directly, to summarize, the proposal is to reverse the resolution in both [#3847](https://github.com/w3c/csswg-drafts/issues/3847#) and [#4915](https://github.com/w3c/csswg-drafts/issues/4915#). (And I'm guessing there might be resolutions related to `color-scheme` and the default `color` value that would need to be reverted, as well?) The reasons why forcing colors at used value time was desirable is well summarized by two of @fantasai's comments: https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-701674628 and https://github.com/w3c/csswg-drafts/issues/4915#issuecomment-707969753. One point of which is how inheritance works when `forced-color-adjust:none` is set (i.e. we would inherit the parent's forced color styles rather than the non-forced color values). This would be a behavior change from what is currently shipped in Chromium. As a result of this behavior change, though, we would no longer need to add `preserve-parent-color` to address the issue raised in [#6310](https://github.com/w3c/csswg-drafts/issues/6310#). And reverting back to forcing colors at computed value time would likely re-raise the following issue: https://github.com/w3c/csswg-drafts/issues/5419#issuecomment-724269096. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1042332194 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 February 2022 21:35:36 UTC