- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jul 2024 07:46:16 +0000
- To: public-css-archive@w3.org
Somewhat related... Sometimes specs:
- disallow whitespace between component values, like `<`, `<type-name>`, and `>`
- require whitespace, like between two `<complex-selector-unit>`s if the `<combinator>` between them is omitted
But it is not explicitly required after `using` in `using ( <dependency-list> )`. Obviously there would be a function if the whitespace was omitted, so this may not be worth clarifying. (Please tell me if I should open a separate issue.)
When a whitespace is missing between two symbols, eg. `<foo><bar>`, it does not mean that a whitespace in the input is disallowed. My point is that if whitespaces were defined to be optionals in a value definition if not explicitly disallowed...
- after `<`
- before `>`
- before a multiplier
- `(` preceding a symbol defining a function's name
- `{` preceding a symbol defining a rule's name
... a syntax like `<function-name>(<declaration-value>#)` for `<dashed-function>` would be unambiguous.
Fwiw, I think this would be confusing and error-prone. A simpler solution is to rewrite with `using <dependency-block>`.
--
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10558#issuecomment-2225017199 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 July 2024 07:46:17 UTC