Re: [csswg-drafts] [css-mixins-1] Do we really need the `@contents` parameter? (#12946)

> or we determine whether a contents block is valid to pass based on whether the mixin uses one in its body

Why is this?

Why can't it be valid when the mixin contains `@content` at least once anywhere in its body?
Is there a constraint or limitation that makes it harder or impossible to determine that a mixin contains `@content`?

-- 
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12946#issuecomment-3417145044 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 17 October 2025 20:52:24 UTC