- From: DarkWiiPlayer via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2023 15:54:10 +0000
- To: public-css-archive@w3.org
The proposal isn't targetting hand-written CSS exclusively, but that is one area where it will be useful. As for the BEM situation, that's basically it, yes. You can axiomatically select elements with a "from to" rule without having to mark every child element with the corresponding parent-component, as long as you can formulate those two selectors properly. Whether this results in reduced complexity of framework code will depend on how much extra logic you need for all those child elements, which would be interesting question for us non-framework-authors, as we can't judge that. I imagine this could also be beneficial for the increased interoperability with non-framework code moving elements in and out of components, but that might not be a priority of most frameworks anyway. As a framework user, I only remember one particular case when fiddling around with svelte where some lines of CSS that would only apply after some slightly hacky logic changing things around, which were just getting thrown out by the framework, presumably because it relied on prefixing all selectors and had no way of doing that correctly. That's sadly too long ago to give a more detailed description of my problem at the time or to really tell if I was really just using the framework in a dumb way or not, but I do think that the simpler CSS that could be generated with `@scope` would have allowed for that to work. -- GitHub Notification of comment by DarkWiiPlayer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1472243392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 March 2023 15:54:12 UTC