- From: Benoît Rouleau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Aug 2024 21:38:46 +0000
- To: public-houdini-archive@w3.org
> I'm open to _allowing_ the guaranteed-invalid value as part of a custom property's value space; there's nothing wrong with `syntax: "<color> | <guaranteed-invalid>"`. But I don't think it's good to make it easy to include it in your value space by default; I'd rather guide people (via the "missing key" errors) to set up their value space properly. @tabatkins – That would be great! If that was supported, I'm guessing setting such a custom property to something that is _not_ a `<color>` would make it guaranteed-invalid instead of reverting to its defined `initial-value`? (Also see my comment [here](https://github.com/w3c/csswg-drafts/issues/5370#issuecomment-2293899627) – it's possible I'm misunderstanding.) -- GitHub Notification of comment by benface Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/994#issuecomment-2294348154 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 August 2024 21:38:47 UTC