- From: andruud via GitHub <noreply@w3.org>
- Date: Fri, 24 Oct 2025 15:02:39 +0000
- To: public-css-archive@w3.org
andruud has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-mixins-1] Mixins can be called (but not defined) without params == It's mildly annoying that you can _invoke_ a mixin without a parameter list (`@apply --m`), but _defining_ a parameter-less mixin requires an explicitly empty list (`@mixin --m()`). It seem more civilized to either make the parameter list optional on the defining side as well, or require `()` when applying a mixin with no parameters. If mixins are indeed going to gain a stronger underlying connection to custom functions (https://github.com/w3c/csswg-drafts/issues/12927), then I'd slightly prefer to just always require `()`, but I'm happy enough as long as we achieve some "symmetry" between `@apply` and `@mixin`. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13015 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 October 2025 15:02:40 UTC