- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Nov 2023 16:57:24 +0000
- To: public-css-archive@w3.org
I think a new generic function is the least weird of the proposed solutions, and the most forwards compatible (I propose `value()`). Special syntax like brackets removes that syntax from the design space for future properties. > Another possibility is continuing to use `,` as a separator, but allowing authors to upgrade to `;` whenever it's needed for disambiguation. Running across a `;` would invalidate the `,` grammar, and re-interpret the function as using `;` separators. We could even do this across all of CSS for consistency. I don’t like this at all. 1. It includes the same cons as semicolons (breaks naive parsers) 2. It introduces more inconsistency: if authors see a `mix()` with semicolons in the wild, it's not clear it also accepts commas and vice versa. 3. Worst of all: it introduces potential breakage that is hard to track down. E.g. is `mix(50%, var(--foo), var(--bar))` correct? Who knows! -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9539#issuecomment-1832334889 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 November 2023 16:57:26 UTC