W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-pseudo] clarify paired-cascading behavior (#6386)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sun, 25 Jul 2021 07:52:22 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-886162393-1627199540-sysbot+gh@w3.org>
>> 1. Does “use” mean used value?
>Hmm, I guess this is underdefined. It could even affect the computed value without causing any problems. Probably the answer here should be whatever seems convenient to implementers. 

I'm not sure. I think it should be used value. One reason is that the UA could decide to paint something fancier than what you could achieve with ordinary values. Using computed values would mean that we need to figure out what that means for animations. If we're in used-value land, that's not a concern.

Even if you're not using fancy things that cannot be represented as a color value, transitions might still be tricky, as I suspect we'd need some special-case code to handle this pair of properties that change value when either of them is asigned something, and that doesn't seem important enough to be worth handling.

Shoving all that to used value means we don't get transitions, and we don't have to deal with any of that.

GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6386#issuecomment-886162393 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 25 July 2021 07:52:23 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC