- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Jan 2024 19:15:08 +0000
- To: public-css-archive@w3.org
> Putting this up on the F2F agenda to discuss. Summarizing the two options:
>
> 1. Remove the `;` separator idea. Instead, use some variety of wrapper for the rare cases when you need to provide a value that is, itself, comma-separated. Options:
>
> 1. Use `[]`, like in Grid to wrap line groups.
> 2. Use `{}`. (Syntax now disallows `{}` at the top-level, but these will be inside of a function, and thus possible.)
> 3. Use `item()` or a similar generically-named function.
> 2. Make `;` an _optional upgrade_. All functions continue to use `,` as the argument separator, but _also_ allow using `;` as a separator. When parsing, assume that `,` is the argument separator at first, but if a top-level `;` is encountered in the function value, re-parse using `;` as the argument separator instead.
We should consider the user experience not only when writing code, but also when *reading* code. The former is only done once, but the latter is done many times. I’m quite concerned that 2 is prioritizing the former over the latter. A grouping construct makes it obvious what is going on, whereas using a different separator only *some* of the time makes parsing hard not just for parsers, but humans too.
--
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9539#issuecomment-1919765900 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 January 2024 19:15:15 UTC