- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Sep 2024 20:25:14 +0000
- To: public-css-archive@w3.org
> I don't get the problem of the trailing comma/semicolon changing the meaning. It already happens with var(): Right, but the syntax there is smaller and easier to spot. An if(), even with a single clause, is gonna be longer than a var(); with multiple clauses there's a lot of text there that might not be noticeable. And if you spread the clauses across multiple lines, like several examples in this thread have done, then a lot of people find it looks much better to put the separator on the final clause; JS has this with arglists and arrays, for example. It is true that some *other* arbitrary-substitution functions can be similarly long and also have this "final comma indicates an empty item" quality, but I don't think it's a particularly *good* thing. It happens, and it's acceptable because we don't have a better indicator, but avoiding it is nice if doing so doesn't otherwise contort the design, imo. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2332570408 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 September 2024 20:25:15 UTC