- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Feb 2022 00:04:48 +0000
- To: public-css-archive@w3.org
Anders points to #6641; in there [I say that "author env()" isn't great](https://github.com/w3c/csswg-drafts/issues/6641#issuecomment-1006172908) because it means that, in many cases, you'll be forced to duplicate the same information in both places. *Most* variables are document-global anyway, so the choice of whether you do it as a var()-on-root or author-defined env() would be mostly arbitrary, and having to decide between the two wouldn't be ideal. I'm supportive of the idea Anders hit in that thread, of allowing these sorts of non-element cases to use the *initial value* of custom properties, which are provided by `@property`. That satisfies the use-case of "author-level env()" while simultaneously continuing to act as a normal custom property. I think that would be appropriate here as well. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6931#issuecomment-1029515775 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 February 2022 00:04:50 UTC