- From: Jonathan Neal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 12:47:23 +0000
- To: public-css-archive@w3.org
@Crissov, solid point on the linters; I’ll try to help with that. I can see about ensuring this in the current tmLanguage (which I think is) used by Atom and VSCode. I’m working on updating the PostCSS syntax to fully respect the css-syntax, and that powers stylelint. If they all follow the css-syntax spec, that might help out with a significant chunk of the linter issues. I’ll write some tests to be sure, but I believe all evergreen browsers parse simple blocks to spec, and therefore support nested semicolons in declaration values. I think fixing these user-land build-time parsers will be faster than updating browser engines (to support component values as property names, plus however that would impact the CSSOM). -- GitHub Notification of comment by jonathantneal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5009#issuecomment-634636466 using your GitHub account
Received on Wednesday, 27 May 2020 12:47:25 UTC