Re: [csswg-drafts] [css-cascade] [css-nesting] Figure out whether we're fine with "shifting up" bare declarations after rules (#8738)

Unfortunately, it appears that Chrome shipped before we could decide on this, and now authors are already [blogging about the "gotcha"](https://kilianvalkhof.com/2023/css-html/the-gotchas-of-css-nesting/).

Hopefully it's not too late to change this. 
I think we should *really* try to avoid any rewriting that changes order of declarations.

Since we’re already [resolved that nested MQs will wrap their contents with an implicit `& {}`](https://github.com/w3c/csswg-drafts/issues/7850#issuecomment-1497794190), perhaps we can do the same thing with any declarations after the first nested rule, as @emilio proposes in the OP?

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1593677467 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 15 June 2023 20:21:50 UTC