- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jun 2024 12:44:32 +0000
- To: public-css-archive@w3.org
Ok, here’s a small scorecard: - Option A: `,`/`;` separator - Option B: `:` separator | Reason | Argues for… | Points | |--------|--------|--------| | Consistency with other CSS functions | A | 2 | | We’re already going with a different separator for the condition, so the ship has sailed wrt consistency with other CSS functions | B | -1 | | `:` was a poor syntactic choice to begin with. The meaning of `:` in natural language is to explain something (e.g. "if(): A conditional function"), not to provide alternatives | A | 1 | | There is no precedent for *both* `if()` *and* `a ? b : c`, in [every other language](https://en.wikipedia.org/wiki/Ternary_conditional_operator) it’s *either* a function *or* a bare `a ? b : c` | A | 2 | | `:` could throw off existing CSS parsers that assume `:` separates properties/descriptors from values. | A | 1 | | Consistency with other C-like languages, including JS. | B | -3 | | `:` is less likely to conflict with the value | B | -2 | | **Total** | Tie! | 0 | Can anyone think of any other reasons? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10064#issuecomment-2167954841 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 June 2024 12:44:33 UTC