- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Fri, 27 Mar 2026 21:57:15 +0000
- To: public-css-archive@w3.org
Yes, changing `{} 1` to be invalid was intentional. I needed the fallback to be *capable* of using `{}` in the new intended manner (as a wrapper that's not part of the value) and didn't want the presence or absence of stuff after the `{}` to drastically affect how we interpreted the `{}` itself. Meanwhile, a fallback value that starts with other stuff (like `1 {}`) is already clearly *not* using `{}` as a wrapper.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12625#issuecomment-4145582555 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 March 2026 21:57:16 UTC