- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Nov 2023 18:30:50 +0000
- To: public-css-archive@w3.org
> Giving functions access to outside variables would also make it more difficult to work with functions generically… The argument is different for mixins… Lea only listed this as a requirement for mixins, so I don't think there's any disagreement here. > > Non-conditional @-rules in mixins. Think of fonts, animations, custom properties, font palettes, https://github.com/scope etc. > > Only insofar as these rules already work when nested inside of style rules. When they do, they should work in mixins; when they don't, they shouldn't. This gets to the question of top-level mixins, which are a fairly common pattern in Sass. I regularly use mixins to generate code (like font rules and keyframes) at the root of the CSS document, not in any nested context. I'm not sure how that would work with a nesting-driven approach to mixins, but there is certainly a use-case for it. On the other hand, it's a use-case that may not have any advantages running on the client. And it's most often used to access flow control and loops, which we don't have at this point. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1806225831 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 November 2023 18:30:52 UTC