[csswg-drafts] [css-conditional][css-mixins][css-cascade] How should global at-rules work inside of "contextual conditionals" like `@container`? (#12627)

tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-conditional][css-mixins][css-cascade] How should global at-rules work inside of "contextual conditionals" like `@container`? ==
Currently, global name-defining at-rules, like `@font-face`, are allowed inside of "contextually conditional" rules like `@container` or `@scope` (which depend on tree information to resolve), and we just ignore the conditional-ness and define them unconditionally, instead. This came up again for `@mixin`.

We want to be consistent across these similar rules, as much as possible. Is the current behavior (which wasn't intentionally designed, it's just what implementations happened to do) what we want to continue with? Or do we want to try and change things so that using these at-rules inside of contextual conditionals is invalid?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12627 using your GitHub account


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

Received on Wednesday, 20 August 2025 08:03:59 UTC