- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Sun, 21 Sep 2025 14:17:20 +0000
- To: public-css-archive@w3.org
> It looks like some of the ideas in here rely "element context" being available at the time mixins are applied. For example, `@apply call(if(style(--is-foo: bar): --bar-mixin))` effectively requires the same context as `@apply call(var(--my-mixin-name))`, and that is quite impossible with the direction the spec is taking; mixins are applied at a time when we know nothing about elements at all. > > (Should be fine for custom functions, though.) I think that's very unfortunate, but should be discussed in a separate issue. That's another advantage of pursuing this as a syntactic transformation: if/when this is fixed in mixins, we get all these use cases for free, but being able to construct function tokens in the same way we can construct idents with `ident()` is useful independently. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12806#issuecomment-3316023611 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 September 2025 14:17:21 UTC