- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Sep 2021 23:52:25 +0000
- To: public-css-archive@w3.org
It might have been worthwhile to use the semicolon in `var()` originally; I didn't because it wasn't strictly necessary, and I don't think it's useful to introduce it *now* since `var()` has been stable and well-supported for years. But yeah, there's a very limited set of characters that are suitable for separating values, and we're already using several of them in CSS. Whatever we choose is then locked out from *ever* being used in CSS as a top-level token in a property value. Semicolon is one of those, and it's *already guaranteed* to never be used as a top-level CSS value, so it's 100% future-safe. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/581#issuecomment-928465844 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 September 2021 23:52:27 UTC