- From: Tobi Reif via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jun 2018 07:24:52 +0000
- To: public-css-archive@w3.org
> that's not a viable possibility. If I understand you correctly it is a viable/possible option but it would require unbounded lookahead in CSS parsers. >From your draft: "this drawback is generally considered unacceptable among popular implementations of CSS." Are there sources for this? Is it a performance issue? > It also privileges the descendant combinator, which isn't ideal. Can you elaborate? Thanks in advance! As for most feature wishes: The main objective (speaking for myself) is to get the feature, the rest is just details. I'd strongly prefer not being required to prepend an ampersand to every single nested rule, and I hope that spec writers and implementers find a way to avoid that (perhaps it could be prototyped and tested and perhaps the perf impact is not really noticeable), but I'll sure take the feature even with that tedious requirement. -- GitHub Notification of comment by tobireif Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2701#issuecomment-393789885 using your GitHub account
Received on Friday, 1 June 2018 07:25:38 UTC