- From: andruud via GitHub <noreply@w3.org>
- Date: Thu, 26 Mar 2026 11:17:29 +0000
- To: public-css-archive@w3.org
All prior discussion took place under the obsolete order-dependent lookup model, so all of that is not very relevant anymore (including the original question). If we close this and do nothing, mixin names will now just get the default behavior of being [loosely matched](https://drafts.csswg.org/css-shadow-1/#tree-scoped-name-loosely-matched) tree-scoped names, which is what I think we should do. This issue remains open due to this comment from @emilio: > I wouldn't expect to be able to apply mixins across trees tbh In other words, we have to figure out if we have reason to make mixins names [strictly matched](https://drafts.csswg.org/css-shadow-1/#tree-scoped-name-strictly-matched) instead. If we do have a sufficiently good reason, I'm fine with making them strictly matched (though it allegedly defeats @sorvell's primary use case). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12671#issuecomment-4133748926 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 March 2026 11:17:30 UTC