- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 12:24:37 +0000
- To: public-css-archive@w3.org
> If we didn't have an indicator of a contents-block argument, then, our behavior needs to be inconsistent in some way: either contents block is always valid to pass even if the mixin doesn't expect or use it, or we determine whether a contents block is valid to pass based on whether the mixin _uses_ one in its body. +1 on being consistent. As arguments are currently defined, I think it makes most sense to determine whether the mixin uses an `@contents` in its body. And if it doesn't, `@apply`'s having a block are invalid. No need for redundancy. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12946#issuecomment-3406148085 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 October 2025 12:24:38 UTC