- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Jan 2023 20:54:58 +0000
- To: public-css-archive@w3.org
The problem is that the current proposal does not match the "common usage of nesting across more than a decade of preprocessors". It already diverges by requiring prefixes in a significant percentage of the cases. As an example, I have a number of projects using the StencilJS framework. That framework requires scoping every custom element style rule with an element selector. The stylesheets is these projects have all sorts of repetition and would benefit greatly from nesting. Over 90% of those style rules would require prefixing in the current proposal. I also have to point out, again, that the rules for when prefixes are necessary aren't as simple as you represent. To this date I have *never* seen a public-facing description of the nesting syntax that accurately describes what an ident is. I've heard too many times to count, and even from Google implementers, that it's easier to simply prefix every nested rule. > and there's no middle ground between our two positions to make a compromise possible And here's the elephant in the room. There **is** a middle ground that satisfies my objection and actually does allow the common usage of nesting. We relax the lookahead requirement. This gets rid of all required prefixes and doesn't impose any restrictions on the evolution of CSS, in fact it opens up more avenues. The problem is that Goggle's position here so far has been "non-starter, we're not even going to consider this", with no data or explanation why. Even though other implementers have said it seems doable and are willing to experiment. I don't believe Google's position here is an example of engaging in the standards process constructively. If there were hard data showing why adding lookahead *can't* be done, then we'd be in a position where we have to compromise on something else, but there isn't, and we don't. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1380983256 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 January 2023 20:55:00 UTC