- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2022 23:38:14 +0000
- To: public-css-archive@w3.org
I [implemented `color-contrast()` in chromium](https://chromium-review.googlesource.com/c/chromium/src/+/3232100) a little while ago, but I've been holding off on shipping it because I got feedback that I was doing the whole calculation at parse time instead of used-value time, which was making it not work properly with `currentColor`. I guess I sort of assumed that color-contrast was already specced to be resolved at used-value time instead of parse time, but now that I see this issue I'm not so sure. I'm having a hard time fully following the discussion here, but is the idea that we should make color-contrast get resolved at used-value time and support currentColor? Are there any WPTs for this? (I don't know what the difference is between used-value time and computed-value time) cc @andruud -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7302#issuecomment-1144249279 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 June 2022 23:38:16 UTC