- From: Alan Stearns via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Apr 2023 23:53:22 +0000
- To: public-css-archive@w3.org
OK, here’s where I think we should move subtopics from this issue: **Issues with error-recovery** -> https://github.com/w3c/csswg-drafts/issues/8349 **Restrictions on future-syntax** -> https://github.com/w3c/csswg-drafts/issues/8251 **Using SASS-like syntax, but not matching some SASS behavior** This has been discussed in a few issues like [2937](https://github.com/w3c/csswg-drafts/issues/2937) and [3748](https://github.com/w3c/csswg-drafts/issues/3748), where we have decided for the most part not to worry about this. If anyone is still concerned with the differences, please open a new issue. **Parsing changes are risky** -> https://github.com/w3c/csswg-drafts/issues/7961 **Unintuitive cascading behavior when declarations come after rules** We have gone back and forth a few times on whether we should allow declarations after rules, and if we do how do we handle them (in the cascade and in CSSOM). I have not found a single issue that seems like an apt place to continue this discussion, so I think we should have a new issue on this. -- GitHub Notification of comment by astearns Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1506110919 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 April 2023 23:53:23 UTC