- From: Raphael via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Jun 2024 08:16:58 +0000
- To: public-css-archive@w3.org
@Loirooriol tl;dr Make a valid empty custom prop (or a space variable placeholder for that matter) more readable and explicit. > Why is it a hack to use a space? That is the name you can find it under and the CSS community refers to when using it. > Note you don't even need a space, --foo:; is valid too. Aye, I know. That is true, but that does not make the readability issue any better. > Would valid-empty just behave as a valid sequence of no tokens? I am not sure I can answer this. But in my opinion `valid-empty` would be a CSS-wide keyword. > Why would this be useful? To me having an explicit keyword to set the value of a custom property to `guanranteed-valid` would be consistent in how you manually reset a custom property to `guanranteed-invalid` by using `initial` keyword. > If you dislike empty values, why not just use --foo: /*valid-empty*/;? I am not _disliking it_, it is more to have an explicit keyword. But having comments looks even more hackier to me. -- GitHub Notification of comment by raphaelokon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10441#issuecomment-2169201673 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 June 2024 08:16:59 UTC