- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Nov 2023 18:06:04 +0000
- To: public-css-archive@w3.org
Right, I think that @Loirooriol is just saying that they'd prefer we explicitly state that, in cases where you could potentially include a value with commas in it, you can only do so if you use semicolons; we will *never* parse a production that includes commas alongside other comma-separated arguments. We'd probably address this at the level of where we define functional notation; we'd say that, unless otherwise specified (such as in `var()`), commas *always* separate arguments (aka are top-level in the function's grammar, rather than being claimable by productions) unless a semicolon is present instead. This might require a little bit of review of existing functions, like gradients have commas in their color-list production and will need that explicitly called out as allowed. (Or maybe we actually reify the concept of "arguments" and say that commas are *solely* for separating arguments, unless semicolons are used instead. But that'd require a larger review of existing spec text. Might still be a good idea, tho.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9539#issuecomment-1830407497 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 November 2023 18:06:06 UTC