- From: Romain Menke via GitHub <noreply@w3.org>
- Date: Wed, 02 Sep 2026 08:07:38 +0000
- To: public-css-archive@w3.org
> > Applying a mixin with @apply effectively substitutes the mixin in-place, so a mixin sees any private properties visible to the style rule it’s substituted into (if it doesn’t override them with its own mixin parameters or private properties).
> This seems weird to me. It kinda breaks the entire premise of @private making things private.
I think I initially also interpreted the current spec as implying that mixins could influence private properties outside of themselves.
Basically:
```css
@mixin --a() {
@private { --foo: 10px; }
}
div {
@private { --foo: 2px; }
@apply --a();
margin: var(--foo); /* influenced by the mixin and now 10px */
}
```
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/14408#issuecomment-5506499755 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 September 2026 08:07:39 UTC