- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 03 Mar 2026 23:29:09 +0000
- To: public-css-archive@w3.org
I don't think "valid" default values are at all reasonable as a general case here, yeah. Like, there's *no way* for us to know that an empty string is a reasonable default for a `<string>` value. Numerics are *usually* 0, but definitely not always. etc. Defaulting *all* the descriptors to what an unregistered normal property does seems like the right thing to me. Syntax of `*`, initial value of guaranteed-invalid, inherits of `true`. That's both simple (good) and I think gives reasonably useful behavior in all provide/omit possibilities. And yeah, I've hit the issue *while writing `@function`'s spec* that it's a little annoying a custom property registration with a type can't still default to guaranteed-invalid; I didn't realize while first defining it that that would be useful, but it definitely is. In the spec I can just *say* that the registration has that initial value (and note that it's not something authors can do), but it would be useful to make it real. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13211#issuecomment-3994207379 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 March 2026 23:29:10 UTC