- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 20:36:56 +0000
- To: public-css-archive@w3.org
> Ok. It seems to me that this is also communicated by not using @contents anywhere in the mixin – and that could also be used as a sign to flag an error? I'm not against it strongly, just don't see much utility from it. Issue is that a mixin might - as either a temporary thing during debugging or intentionally because there's multiple versions of a mixin and only some of them actually use it - lose its `@contents` rule. It'd be annoying if that would cause invocations that pass a contents block to start failing. I usually prefer leaning into Python's "explicit is better than implicit" philosophy with things like this, when I can. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-3080465665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 20:36:57 UTC