- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Aug 2022 20:11:02 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `color-contrast() with automatic continuous lightness adjustment`, and agreed to the following: * `RESOLVED: Defer for now` <details><summary>The full IRC log of that discussion</summary> <emilio> Subtopic: color-contrast() with automatic continuous lightness adjustment<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/5153<br> <emilio> lea: so this is similar to the previous problem we discussed where you have a given color and you want to lighten or darken it enough so that you get decent contrast<br> <emilio> ... I think in this case the contrast does tend to be monotonic<br> <emilio> ... so you might be able to binary search<br> <emilio> ... we could punt as well for now<br> <emilio> TabAtkins: I don't think this one is problematic but might be worth punting for the moment<br> <emilio> q<br> <emilio> q+<br> <emilio> miriam: I think this is useful, it's something that a preprocessor can do in a bunch of cases, but it's ok if we delay it<br> <emilio> astearns: people want to ship contrast-color() so the simpler the better for now<br> <fantasai> emilio: was going to mention, what we use internally for a lot of these use case<br> <fantasai> emilio: it's not lightness, luminance more generally<br> <fantasai> emilio: in order to replicate a default color palette with an arbitrary accent color<br> <fantasai> emilio: we have a function to adjust the function to a given luminance<br> <fantasai> TabAtkins: that's just relative color syntax<br> <astearns> ack emilio<br> <fantasai> emilio: I think unless we have any pressing issue, I vote to punt<br> <fantasai> emilio: this seems extremely similar to what we discussed<br> <fantasai> emilio: so maybe punt<br> <emilio> RESOLVED: Defer for now<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5153#issuecomment-1203167330 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 20:11:04 UTC