W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2016

Re: [csswg-drafts] [css-ui-3] caret-color animations, 'auto' and 'currentColor'

From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Dec 2016 04:05:27 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-264368623-1480651525-sysbot+gh@w3.org>
> would it be possible that the computed value of `currentColor` and 
`auto` would be a `rgb()` (like it happens for the rest of color 
properties)?

No. Computed value of `currentcolor` is the keyword `currentcolor`. 
The text you referenced from CSS Color 4 also indicates this. It is 
only resolved at used-value time, not computed-value time. And this is
 necessary for color properties which are inherited by default 
(`text-emphasis-color` and `-webkit-text-*-color`).

As for `auto`, I am not really happy with adding another 
computed-value time keyword to `<color>`. It would be hard to 
implement as I've mentioned in [a 
comment](https://github.com/w3c/csswg-drafts/issues/364#issuecomment-237151348)
 of w3c/csswg-drafts#364.

I think, `auto` should be defined to not be interpolatible with 
`<color>` values, and I don't think that would be a big issue. Authors
 should specify `currentcolor` or numeric color values if they want 
animation on this property.

-- 
GitHub Notification of comment by upsuper
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/781#issuecomment-264368623 
using your GitHub account
Received on Friday, 2 December 2016 04:05:35 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:26 UTC