- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Jul 2020 11:46:53 +0000
- To: public-css-archive@w3.org
Central to the design of css-variables is the idea that whatever their value, the cascade doesn't change. This proposal would change that assumption. I do like this idea, but I have a hunch someone familiar with browser internals will be along at some point to say it's more expensive to implement than it looks. See for example the following note in [css-variables-4](https://drafts.csswg.org/css-variables/#using-variables): > Note: The invalid at computed-value time concept exists because variables can’t "fail early" like other syntax errors can, so by the time the user agent realizes a property value is invalid, it’s already thrown away the other cascaded values. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5319#issuecomment-659358735 using your GitHub account
Received on Thursday, 16 July 2020 11:46:55 UTC