- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Jul 2018 18:36:07 +0000
- To: public-css-archive@w3.org
This can't be done for unregistered custom properties. It's just as valid to *want* the substituted value to be resolved on children, fetching *their* attribute value, not the ancestor's. For a registered custom property (see [Properties & Values API](https://drafts.css-houdini.org/css-properties-values-api/)), attr() will always be resolved immediately, because they process their values right away. I do have future plans to allow people to *declare* that an unregistered custom property should be immediately evaluated according to some grammar, so you could cause this sort of thing to happen on command, but I'm not currently working on Variables 2, where it would go. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2946#issuecomment-407158361 using your GitHub account
Received on Monday, 23 July 2018 18:36:09 UTC