- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Apr 2024 04:24:22 +0000
- To: public-css-archive@w3.org
> More complicated for browser engine indeed, but less complicated for CSS users Not sure I agree. This requires to expand the API surface of CSSOM quite a bit, or changing APIs in ways that are confusing / inconsistent (like not returning rules from .cssRules), or unclear... If you're not inspecting stylesheets via script, it doesn't matter either way. If you do, then IMO the `@nest` rule is easier to deal with than something new / more complicated. It just works like a style rule. Given that, and that this is somewhat of a time bomb which we probably want to fix sooner rather than later, I tend to think that the simplest / less magical solution is best. * It's implementable in a very straight-forward / performant way in all engines. * It raises less open / follow-up questions. * It's (IMO) not worse for authors than the current state of things or alternatives. @tabatkins regarding the proposal, I'm assuming: * `@nest` doesn't need to be a grouping rule (though I guess it doesn't matter much either way). * With "style rules" in your proposal you mean style declarations, presumably, right? -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-2060318199 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 April 2024 04:24:23 UTC