- From: Benoît Rouleau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Aug 2024 17:36:59 +0000
- To: public-css-archive@w3.org
I know this issue was closed, but it seems like this comment from @tabatkins was never addressed: > This isn't an unreasonable request! In [w3c/css-houdini-drafts#994 (comment)](https://github.com/w3c/css-houdini-drafts/issues/994#issuecomment-663316332) Amelia asks for the ability to explicitly allow a registered property to still assume the guaranteed-invalid value, which is currently only possible when you have a completely unrestricted grammar. Implicitly, this is recognizing that the guaranteed-invalid value actually is "valid" in some circumstances; it's guaranteed to never match the grammar of any predefined CSS property, but it's part of the value space (and thus, matches the grammar) of unregistered custom properties, or registered ones with unrestricted grammar. It's possible I'm missing something, but it seems there is still no way to make the initial value of a _registered_ custom property with a syntax other than `*` the guaranteed-invalid value? That would be super useful IMO to enable fallbacks in `var()` when the custom property is set to an invalid value (instead of resetting it to some global initial value that may not work in the current context). I really like the `initial-value: initial` proposal by @AmeliaBR in that `css-houdini-drafts` thread. 👍 (But I hope I'm missing something and it's already possible, please let me know if that's the case!) -- GitHub Notification of comment by benface Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5370#issuecomment-2293899627 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 August 2024 17:37:01 UTC