- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Fri, 13 Jun 2025 23:05:26 +0000
- To: public-css-archive@w3.org
I don't think I see the reason to do a "generic" at-rule that still has to specify what type of condition it's for. At that point you're just shifting the specifier around, and it's more ergonomic to put it in the name of the at-rule instead.
That is, `@prelude --foo { syntax: "@media"; value: (width >= 768px); }` is identical to `@custom-media --foo (width >= 786px);`, but the latter is shorter and gives us a better ability to expose a half-useful CSSOM class (and better tooling in general).
And I think I agree with Anders that allowing a single rule to specify a value for multiple types of rules isn't great, since their syntaxes only overlap by accident.
I'm okay, I think, with a proliferation of `@custom-<condition>` rules; we don't have too many of them *anyway*, and it makes things clearer overall.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7622#issuecomment-2971921428 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 June 2025 23:05:26 UTC