- From: Steinar H. Gunderson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 16:06:13 +0000
- To: public-css-archive@w3.org
> Why not adopt the SCSS syntax entirely ?
As has been discussed in the thread already, and also noted in the draft standard, the case of “nested-tag {}” would be ambiguous to parse without increasing the parser's lookahead (either explicitly or by implicit means, such as restarts).
> I know it could cause parsing issue of existing CSS, but we already had a similar problem with HTML5. So we simply created a new Doctype to handle that.
The word “simply” is not one that comes to mind if you're suggesting maintaining two entirely separate CSS parsers indefinitely (both in the spec and in code).
--
GitHub Notification of comment by sesse
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1302333016 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 November 2022 16:06:15 UTC