From 9342380bd185335477a6367e8ffc293aab6b3a37 Mon Sep 17 00:00:00 2001 From: Miriam Suzanne Date: Tue, 11 Jun 2024 12:16:44 +0200 Subject: [PATCH] Add summary --- content/blog/2024/removing-mixins.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/content/blog/2024/removing-mixins.md b/content/blog/2024/removing-mixins.md index fc9c22f7..70296a67 100644 --- a/content/blog/2024/removing-mixins.md +++ b/content/blog/2024/removing-mixins.md @@ -12,14 +12,17 @@ tags: - CSS - CSSWG - Mixins & Functions +summary: | + The CSS Working Group + has agreed to move forward + with CSS-native mixins. + But some recent mixin-like + CSS tricks have an advantage + that the official proposal doesn't account for: + they make it easy to remove a mixin + after it's already been mixed in. --- -I've been thinking about -[CSS-native mixins](https://css.oddbird.net/sasslike/mixins-functions/). -How do we create re-usable blocks of styling -that can be 'mixed in' to various selectors, -based on arbitrary conditions? - {% callout 'CSS Layout Workshop' %} If you have questions about this feature or others like it, we'll be getting deep into modern CSS @@ -30,6 +33,11 @@ at the **Cascade Layouts Workshop**, June 24-26. ## Mixin substitution with `@apply` +I've been thinking about +[CSS-native mixins](https://css.oddbird.net/sasslike/mixins-functions/). +How do we create re-usable blocks of styling +that can be 'mixed in' to various selectors, +based on arbitrary conditions? I made [a proposal](https://css.oddbird.net/sasslike/mixins-functions/) last year, and it was [adopted by the CSS Working Group](https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1939628591)