- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Feb 2024 07:30:36 +0000
- To: public-css-archive@w3.org
I would want to point out that the differences between `@mixin` and something like `@same-as` are not just syntactic. The way I see it, the most powerful thing about `@same-as` is that it does not necessarily require a shared "contract" between the mixin and the mixin usage, because _anything_ can is a potential mixin. This would enable libraries and components to adapt to the surrounding page with very little integration effort from authors. As a library author, I'd sacrifice mixin parameterization to get that **in a heartbeat**. But like I said, I suspect it would not be feasible. That said, we should definitely explore feasibility, rather than ruling it out upfront. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-1968386856 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 February 2024 07:30:37 UTC