- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jan 2022 13:48:51 +0000
- To: public-css-archive@w3.org
> Having an author-defined env() might work, but would require an author to duplicate values across properties and env(), or else decide for each whether they want to express it as a var or an env(). Yeah, I see how that would be annoying. OK, then maybe we can specify that `var()` in non-element contexts use the initial value of custom properties, and then provide a new way of specifying those initial values (if `@property` is too verbose). > Would [root special case] be reasonable impl-wise? If we're going to generalize that, I suspect that creates way more complexity than it's worth. We'd be smuggling in the full weight of "computed-value-time", and we'd be unable to interpret any at-rules sooner than that, which is probably not a good thing. For example, the custom properties on :root may be animated, or they may depend on the computed font metrics of the selected font (e.g. with `--x:10ch` + `@property` with `syntax:"<length>"`. Fun times if `var(--x)` is then used in `@font-face` somehow). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6641#issuecomment-1006605654 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 January 2022 13:48:53 UTC