Re: [csswg-drafts] [css-mixins-1] How should missing non-defaulted arguments for custom functions be handled? (#14165) from Tab Atkins Jr. via GitHub on 2026-07-10 (public-css-archive@w3.org from July 2026)

From: Tab Atkins Jr. via GitHub <noreply@w3.org>
Date: Fri, 10 Jul 2026 22:02:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-4939885264-1783720972-noreply@w3.org>

Okay, right, on reviewing, the intended behavior is indeed that if the arg doesn't have a default value, it must be passed or else the entire call is invalid. I'll fix the spec to make that clearer.

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


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

Received on Friday, 10 July 2026 22:02:55 UTC