Re: [csswg-drafts] [css-color] color-contrast() default algorithm (#7361)

The CSS Working Group just discussed `default algo`, and agreed to the following:

* `RESOLVED: We have an unspecified default, the best available to the UA, which gets updated, only when there aren't any candidates. If you include any candidates, algorithm is mandatory`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> Subtopic: default algo<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7361<br>
&lt;chris> q+<br>
&lt;astearns> ack una<br>
&lt;emilio> una: I really like having no algo specified, just the value you want contrast against<br>
&lt;fantasai> emilio: if you fall off the list, do you implicitly end up with white and black and if white passes contrast testing...?<br>
&lt;TabAtkins> TabAtkins: No, you take the one that's more contrasting<br>
&lt;florian> q?<br>
&lt;fantasai> chris: They're not tried in order, just either give me white or black<br>
&lt;florian> q+<br>
&lt;lea> q+<br>
&lt;fantasai> TabAtkins: if you want to specify the order, give a list<br>
&lt;lea> q-<br>
&lt;chris> q-<br>
&lt;lea> emilio: this is why it's not unfortunate that we're maximizing: color: color-mix(contrast-color(over var(--color), var(--color) 20%);<br>
&lt;astearns> ack florian<br>
&lt;emilio> dbaron: open to default in the future right?<br>
&lt;emilio> TabAtkins: yes<br>
&lt;dbaron> (I was responding to a statement of the proposed resolution that wasn't minuted.)<br>
&lt;emilio> florian: so options are either contrast-color(over ...), or contrast-color(over foo &lt;algo>, a, b, c..) right?<br>
&lt;emilio> astearns: objections with going with (4) + (5)<br>
&lt;emilio> Proposed: We have an unspecified default, the best available to the UA, which gets updated, only when there aren't any candidates. If you include any candidates, algorithm is mandatory<br>
&lt;fantasai> contrast algorithm is optional, and defaults to the best available to the UA (which gets updated over time),  if no candidate colors are specified<br>
&lt;fantasai> yes<br>
&lt;emilio> RESOLVED: We have an unspecified default, the best available to the UA, which gets updated, only when there aren't any candidates. If you include any candidates, algorithm is mandatory<br>
</details>


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


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

Received on Tuesday, 2 August 2022 18:43:47 UTC