- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2025 04:26:31 +0000
- To: public-css-archive@w3.org
> > allow whitespaces between a function name and ( > > Nothing to be discussed here, no whitespace is allowed. That's consistent for all functions in CSS. You started discussing this in the [comment](https://github.com/w3c/csswg-drafts/issues/10558#issuecomment-2226420917) above: > I think we should probably at minimum switch to that; possibly we can allow both forms, if useful. This is a novel syntactic form, so even tho it's kinda unprecedented, that might still be acceptable. I do not want to continue a discussion that is already over, but if I see `fn (a)` in a value definition, is that allowed? does it represent a function or a keyword and a simple block? > Sure you can. `<dashed-function>` is defined in the Mixins spec, it's perfectly usable as a non-terminal. It is true. I thought about the problem wrongly. Sorry. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10558#issuecomment-2683862455 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 February 2025 04:26:32 UTC