Re: [csswg-drafts] [css-mixins-1] Using a scoping rule breaks author expectations, can we get rid of it? (#13727)

> PROPOSED: Drop https://github.com/scope'ing from @mixin. Values that can't resolve because they're outside the subtree are guaranteed-invalid.

> SUMMARY: Look into some ideas around merging @mixin and @macro.

I hadn't followed this closely enough to even see `@macro` before this. The distinction between `@macro` an `@mixin` feels clunky and dropping it seems better, if possible.

For cross-scope styling, I pretty much always want scoping but am fine with just doing something like this:

```css
.partLike {
  @scope(&) { @mixin --my-theme(var(--primary-color)); }
}

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


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

Received on Thursday, 2 April 2026 00:29:59 UTC