Re: [csswg-drafts] [css-mixins] `<dashed-function>` syntax seems invalid (#10558)

@cdoublev Thanks for reviewing this spec.

> `--*() = --*( <declaration-value># )`

Yeah, I had no idea how to express the thing that needed expressing here. This was inspired by [--*](https://drafts.csswg.org/css-variables/#defining-variables) from css-variables-1. `<dashed-function> = --*( <declaration-value># )` looks better.

What does it mean to mark it `informative`, and how do I do that?

> @andruud , did you intend to write both of these locations with that whitespace, or was it unintended?

Not exactly intentional. I based this on [Miriam's explainer](https://css.oddbird.net/sasslike/mixins-functions/#defining-a-function-the-function-rule), and then forgot to think about whitespace while copying that grammar.

I agree that `@function --foo()` should work. And _probably_ it should be the only valid form?

Not sure if that means we should require `using(` as well. Although really I'm hoping we can find an alternatively way to represent the dependencies which avoids the issue.

-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10558#issuecomment-2255462820 using your GitHub account


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

Received on Monday, 29 July 2024 09:38:21 UTC