- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Thu, 04 Dec 2025 01:21:49 +0000
- To: public-houdini-archive@w3.org
> Mass registration with wildcards: so ... `@property --int-*` is basically something like a "selector" that "matches" custom property names on that form? I'm not sure if it's wise to bake that much (potentially expensive) complexity into the the computed value process. Hopefully we can consider other ways to solve the use-cases this would be needed for. For example, custom functions/`if()` could help for some of them?
I do think we should introduce features that eliminate the need for the **hundreds** of custom properties currently needed by design systems, but I don't think we'd ever get it down to such small numbers where mass-registration won't be desirable. And there is a nice decoupling in being able to write
```css
@property --foo-color-* {
syntax: "<color>";
initial-value: transparent;
inherits: true;
}
```
rather than having to list every color design token in a centralized place.
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1058#issuecomment-3609518789 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 December 2025 01:21:51 UTC