- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Dec 2019 22:14:51 +0000
- To: public-css-archive@w3.org
Ah, I did indeed misread the issue. The mechanics of "allow a var() to resolve to a CSS-wide keyword" should be the same as the current "var() becomes inherit/initial if it's the guaranteed-invalid value". Late-resolving a var() (fetching the custom property value at time of var() resolution) has no mechanical problems either, but it does has some design issues. tokens() would be a "use once" thing - if you build up a variable from other variables, they'll be resolved at the middle stage, rather than at the ends. I guess you could wrap tokens() around itself multiple times, so each substitution stripped one layer off, but that requires a fragile prediction of how much you'll do, and might not even be possible if the build-up is based on depth. Maybe it's ok that it'll only survive a single substitution? Or maybe it survives *all* substitutions, and you have to explicitly un-raw it with another function when you want the substitution to happen. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2749#issuecomment-565628592 using your GitHub account
Received on Friday, 13 December 2019 22:14:53 UTC