Re: [csswg-drafts] [css-mixins] Disallow whitespace when matching `'<' transform-list '>'` (#10560)

As noted in #10558, disallowing whitespace in these places sets a precedent whereas it seems unambiguous to parse.

In my humble experience, spec authors often omit whitespace in various cases:

  - `a| b`
  - `<a><b>`
  - `[a b ]`
  - `fn( a b)`

They can all be parsed fine. I expect CSS authors to also omit whitespaces. This may be relaxed later, but perhaps they would appreciate some forgiving syntax.

I think functions are the only ambiguous case: there should be no whitespace between the expression representings its name and `(`. `@function` (or maybe later in `syntax` for `@property` and the first argument of `<attr()>`), does not allow representing them though.

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