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

I mentioned this in one of the calls, but I figured I should write it here too for posterity: The past couple of months I have experimented with teaching novices CSS nesting from the start, as it's a *much* more straightforward way to explain things than descendant selectors. I did not mention anything about the order of declarations and rules and left it up to them. Almost everyone’s code that I have seen naturally ends up having declarations interleaved with rules. 

My takeaways:
1. So, _so_ glad we ended up with one of the options that allowed this.
2. We _need_ to fix this issue, ASAP. The hidden `@nest` approach outlined above seems to work well, for both authors and implementors. What's the blocker?

@tabatkins nit, but I wonder if `@this` might be a better name? Since it's not really nesting?

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


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

Received on Wednesday, 10 April 2024 13:41:17 UTC