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

Re: [csswg-drafts] [css-variables?] Higher level custom properties that control multiple declarations (#5624)

From: Lea Verou via GitHub <sysbot+gh@w3.org>
Date: Fri, 11 Dec 2020 14:06:12 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-743211067-1607695571-sysbot+gh@w3.org>
A few issues with speccing generic comparison expressions: how are certain values interpreted outside of a declaration context? E.g. what are percentages relative to? If we disallow percentages, then I suppose we should define this as a union of specific types (and both sides of the comparison need to be of the same type), i.e. `<dimension> | <color> | <image> ...`. There is `currentcolor` that works differently in `color`, and `em` that works differently in `font-size`. What do we do with them? Are there other values that are ambiguous outside of a declaration context? So far the only values we've allowed outside of declarations are those permitted in media features, which I think are limited to lengths.
Also, I suppose anything that is not a `<number>` or `<dimension>` would only work with equality (and inequality, if we define one, we could also just depend on `not` for that).
Is equality based on serialization of used values? E.g. is `#f06` equal to `#ff0066`? What about to `rgb(255 0 102)`? They all serialize the same.

(this is mostly to @tabatkins but any input is welcome)

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 December 2020 14:06:14 UTC

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