Re: [csswg-drafts] [css-color-adjust-1] Combine forced-color-adjust and color-adjust properties somehow? (#3880)

The CSS Working Group just discussed `Combine forced-color-adjust and color-adjust properties somehow?`, and agreed to the following:

* `RESOLVED: no change, keep both forced-color-adjust and color-adjust`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Topic: Combine forced-color-adjust and color-adjust properties somehow?<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/3880<br>
&lt;dlibby_> leaverou: I was in the breakout, there are many use cases where you want both. should be an easy way to enable both<br>
&lt;dlibby_> leaverou: perhaps a shorthand would provide flexibility<br>
&lt;dlibby_> TabAtkins: i think these are sufficiently different that we shouldn't turn them off at one. printing well is conceptually similar but different that color adjustment for forced colors<br>
&lt;dlibby_> TabAtkins: wouldn't want to trigger one, but accidentally the other (i.e. if authors optimize for screen media, not print)<br>
&lt;dlibby_> TabAtkins: suspect they shouldn't be done at the same time<br>
&lt;dlibby_> Rossen_: in two environments, the properties have almost opposite effect (on-by-default vs. off-by-default)<br>
&lt;dlibby_> Rossen_: historically they have different usage as well, increasing adoption, i'm on the side of keeping these separate for the same reasons<br>
&lt;dlibby_> fantasai: agree with reasons to keep them separate. color swatches is a use case for using them in both situations.<br>
&lt;dlibby_> fantasai: would be nice for authors be able to have something that works for future color adjustments, but currently color-adjust is specific to print<br>
&lt;fantasai> s/a use case/the one use case I can think of /<br>
&lt;dlibby_> Rossen_: Proposed resolution no change - any objections?<br>
&lt;dlibby_> RESOLVED: no change, keep both forced-color-adjust and color-adjust<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3880#issuecomment-816275920 using your GitHub account


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

Received on Thursday, 8 April 2021 22:35:09 UTC