- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Jun 2024 09:02:54 +0000
- To: public-css-archive@w3.org
If I recall correctly, at some point `--foo:;` (and `var(--foo,)` — without a space) was not valid. Right now it is, yes. My main argument is learnability and discoverability: when you see something like this in your code or devtools: <img width="132" alt="A screenshot of chrome devtools showing a tooltip with an empty space" src="https://github.com/w3c/csswg-drafts/assets/177485/aac18bac-f7dd-4b87-88a5-af30e32e5cae"> (there is a tooltip that looks empty) You just see an empty value, which does not tell you anything. You could put the `/* empty */` in the variable definition, but used value somewhere else won't have it. And then CSS minifiers would likely remove the comment, making the source less undersrandable again. When you discover something like that in the wild, and you're an author who does not know about this valid empty value, how would you search for it? A query like “css empty value” won't help, but “css empty variable value” would, but not everyone is good at search, sadly. It is much easier to look for something like “css valid-empty” when you know the keyword. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10441#issuecomment-2169227630 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 09:02:55 UTC