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

Tab already [marked it](https://github.com/w3c/csswg-drafts/commit/71d777bfa5f1ee2bbed3bf62ab2e776d64a1b820#diff-9c4c1c5a9da867a8f9b01470f5918ee9a736bce6ba707c484a34c6e51f8dffb4L216) as *non-normative* with the [`informative` class](https://speced.github.io/bikeshed/#metadata-informative-classes). Now `w3c/reffy` no longer extracts it from the spec.

If I am not mistaken, `<dashed-function>` will never be included in other value definitions, like other substitution functions. So this issue may therefore be considered fixed.

But since it must be syntactically validated, it would be nice to define its syntax using a *normative* value definition.

Fwiw, I like Tab's idea. This requires disallowing function names like `not`, `and`, `or`, right? This would fix #7016 by replacing `<function-token> <any-value> <)-token>` with `<ident> (<any-value>)`.

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10558#issuecomment-2255746650 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 12:02:17 UTC