Re: [csswg-drafts] [css-mixins-1] Do we really need the `@contents` parameter? (#12946) from andruud via GitHub on 2025-10-16 (public-css-archive@w3.org from October 2025)

From: andruud via GitHub <noreply@w3.org>
Date: Thu, 16 Oct 2025 14:10:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-3411092824-1760623809-noreply@w3.org>

So the `@contents` parameter can't do anything that regular parameters can do (have a chosen name, type, default) except _be_ declared. This might be what makes it feel unnecessary and/or out-of-place in the parameter list.

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


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

Received on Thursday, 16 October 2025 14:10:12 UTC