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 09:43:32 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-264413836-1480671810-sysbot+gh@w3.org>
`getComputedStyle()` is not supposed to return the computed value for 
color properties, because that may break web compat, see 
w3c/csswg-drafts#566. In addition, there is currently no stable syntax
 to describe a color combined from numeric color and `currentcolor` in

This is a testcase for whether `currentcolor` is handled as a 
computed-value time keyword: 

In this testcase, `color` is changing in the (paused) animation from 
`#ff0000` to `#0000ff`, while another color property is changing from 
`currentcolor` to `#00ff00`. You can see that
* Chrome shows two blocks both have color `rgb(64, 128, 64)`, which 
indicates that `currentcolor` is handled as computed-value time 
* Firefox 50 as well as Safari shows two blocks with color `rgb(128, 
128, 0)` which means `currentcolor` becomes a numeric color at 
computed-value time.
* Firefox 52 shows one block with `rgb(128, 128, 0)` and the other 
`rgb(64, 128, 64)`, because that version of Firefox has supported 
computed-value time `currentcolor` for `border-color`, but not 

GitHub Notification of comment by upsuper
Please view or discuss this issue at 
using your GitHub account
Received on Friday, 2 December 2016 09:43:39 UTC

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