- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Jan 2024 03:36:53 +0000
- To: public-css-archive@w3.org
I've always thought that there was an implicit `!` on the whole value syntax definition of every property, so that it wasn't necessary to include in cases like this one. If not, I agree it should be added, but given that empty values are never valid based on "what else could it possibly mean", it seems we'd be better off adopting that convention if we haven't already. So, should I add a `!` here, or should we clarify in css-values that it's implied in cases like that, or do we already have that somewhere? cc: @fantasai @tabatkins -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9368#issuecomment-1907299467 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 January 2024 03:36:56 UTC