- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Apr 2024 17:46:56 +0000
- To: public-css-archive@w3.org
> the names would never clash with any future CSS syntax (the names are user-defined by definition)
There have already been proposals for CSS-provided mixins, which would lead to this naming conflict. I don't think it's safe to say these are guaranteed to be user-defined long-term.
I do see advantages to the mixins-as-functions approach. The `colors` example is especially compelling to me. But it does make the simple function syntax significantly more verbose:
```css
.example {
background: --stripes(powderblue, pink, white);
background: apply(--gradient from --stripes(powderblue, pink, white));
}
```
I'm curious how much it would complicate (or simplify?) implementation.
--
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-2048135278 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 April 2024 17:46:57 UTC