- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Jan 2023 00:16:52 +0000
- To: public-css-archive@w3.org
No, "just look for a terminating `;` or `{}`" doesn't work - there are legitimately ambiguous cases *today* (custom properties), and depending on what future syntax changes we add, there may be more. So the rules do need to be set. They're still potentially *changeable*, so long as we're only making previously-invalid things valid, and subject to compat, but they need a stable definition to start from that categorizes the actual ambiguous cases (in addition to the cases that are eventually-unambiguous).
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7961#issuecomment-1397771762 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 January 2023 00:16:54 UTC