- From: Natalie Weizenbaum via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Jun 2022 23:33:36 +0000
- To: public-css-archive@w3.org
> Any serious CSS tooling should have already built in pairing of parens, brackets, and braces, which should render this a non-issue. Why should it? If a tool wants to naïvely determine the start and end of a given declaration, currently it can do so by simply consuming tokens until it hits `;` or `}` and realistically that'll function correctly for essentially all real-world CSS. Yes, there are custom-property edge-cases that will break, but I don't think any of them have seen widespread use since Polymer entered maintenance mode. And that's to say nothing of the undoubtedly countless hacked-together tools that don't even tokenize the input and just use regular expressions to parse. > What specific tools are so naive as to choke on this, and is the breakage really so bad that we need to alter core CSS to compensate? Sass is a specific example of a tool that will choke on this, although not so much because it's naïve as that it needs to do a semantic parse of all expression syntax. The Sass breakage isn't bad enough to be worth altering CSS on its own, since we could easily add support for this new syntax. The core objection here is that it would break *many* tools—particularly small, *ad hoc* tools that are likely maintained by individual organizations rather than widely-used open source tools which have stronger pressures on them to support every edge case. -- GitHub Notification of comment by nex3 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6705#issuecomment-1151712035 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 June 2022 23:33:37 UTC