- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Sep 2024 18:47:09 +0000
- To: public-css-archive@w3.org
Could the IACVT vs empy be solved via something like `valid-empty` keyword, see https://github.com/w3c/csswg-drafts/issues/10441, and treating the actual empty in this case as IACVT? That will make it behave differently from how custom properties currently work, but I find it acceptable. And, as expressed in that other issue, I consider an explicit keyword a better design for this fringe edge case anyway. Especially, given most of the usage for the empty value right now are for conditionals :D Re: the problem with the `<declaration-value>`, I'd +1 to @LeaVerou for disallowing `:` from it. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2327192069 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 September 2024 18:47:10 UTC