- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Jan 2023 20:24:04 +0000
- To: public-css-archive@w3.org
There's no *particular* reason to not require one, but the general policy across all of CSS is that whitespace is always optional, and I'm mildly opposed to adding one-off requirements for it unless there's a good reason; it just makes the language slightly less consistent. (And we probably can't add a general requirement for whitespace between tokens, because I suspect minifiers exist that take advantage of the current rules.) There's not really a "use-case" either way, it's just that comments are a guaranteed way to force a tokenization boundary without whitespace, so we usually reach for them when showing off the parsing. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8285#issuecomment-1376271325 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 9 January 2023 20:24:06 UTC