- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Feb 2024 20:06:13 +0000
- To: public-css-archive@w3.org
After thinking a bit about it, I don't like the idea of magically creating other variables from a map, and will be ok with having just a `get` function, so instead of `opacity: var(--foo-bar)` for getting the value from a `--foo: { bar: 1 }`, we'd have to write `opacity: get(--foo, bar)`, which is almost the same, but more explicit and without the side-effect.
The thing we'd need then is to have something like `@set` or something, which could be then used to set some key to some value for the current map, instead of the proposed way with the `--foo-bar: …`
--
GitHub Notification of comment by kizu
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9992#issuecomment-1965157964 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 February 2024 20:06:14 UTC