W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] [css-color-4] Make system color keywords compute to themselves (#3847)

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Wed, 30 Oct 2019 15:21:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-547960604-1572448872-sysbot+gh@w3.org>
Any impacts regarding animations also affect `currentColor` as an interpolation end point, since `currentColor` is also spec'd to compute/inherit as a keyword. All browsers currently support animating currentColor, as far as I know, so we can't break that. Firefox also successfully inherits it as a keyword, even when animating, but Chrome (and I think WebKit) do not.

Test: https://codepen.io/AmeliaBR/pen/VwwMEqy?editors=1100

Note that, in Firefox, the inherited background color on the div animates between currentColor and tan, even though it has a different currentColor (hotPink) than the parent which defines the animation (alternating navy and red).

> Or we have special rules to define that animations between colors use their resolved values.

I'm not sure how this would work for the cases in the demo, where the reference colors change during the animation, and where the animated value is inherited.

I'd rather just jump ahead an introduce an interpolation function to describe the intermediary computed state of `interpolate(50%, currentColor, tan)`.

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3847#issuecomment-547960604 using your GitHub account
Received on Wednesday, 30 October 2019 15:21:15 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC