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

> Right, same applies to simplifying mixins by removing an argument, currently.

No, it doesn't apply the same, that's my point. If you are playing around with a Mixin and temporarily *stop using an argument in the body*, all your `@apply`s still work. Whether you *use* the arg or not doesn't matter, just that it's specified in the arglist. That's the behavior I was trying to maintain, with the `@contents` in the arglist.

The only reason you'd have to go back and edit your call sites is if you actually *remove the argument from the arglist*, because you've decided you don't need that argument at all, permanently. That's perfectly reasonable.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12946#issuecomment-3408363804 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 21:29:29 UTC