- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 21:34:14 +0000
- To: public-css-archive@w3.org
> I have some concerns about assuming mixins can only impact descendants - though it certainly does help sidestep the question of where variables resolve. Right, we definitely need to *allow* affecting non-descendants, you just won't get the nice var()/em/attr()/etc behavior if you opt into that. It's a tradeoff the author has to make: hygienic arguments, or unscoped application. > If we do assume this, then :scope in a mixin refers to the applying element? I suppose so, for consistency. Probably not strictly required, but I don't think it matters much either way. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12927#issuecomment-3408383992 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:34:15 UTC