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: Thu, 10 Dec 2020 12:16:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-742485297-1607602573-sysbot+gh@w3.org>
IACVT could work for components, since presumably all their styles are defined in the same place. Assuming these rules can be nested with predictable results, and do take all values defined in the rule into account before triggering IACVT (per @FremyCompany and @brandonferrua's suggestions), I don't think the downsides of IACVT will come into play too frequently. However, especially in that case, nesting support becomes *really* important.

I love the idea of using `var()` instead of `<dashed-ident>` so we can compare any two expressions, not just variables. E.g. this opens the door for conditionals like `1em < 16px`, so it's a strictly more powerful feature. We should probably define these comparison expressions separately, in Values & Units, and reference them in any other spec that needs them.

Indeed, `not`, `or`, and `and` operators should certainly be allowed, most likely with mandatory parentheses like in `@supports`. 

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 December 2020 12:16:16 UTC

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