- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Jun 2023 22:24:58 +0000
- To: public-css-archive@w3.org
I still feel very strongly that we should not change this, and the current behavior is the best. Again, this is the *exact* behavior that Sass (and I suspect other preprocessors) have had for a decade+ already, and it has not been a problem there. (Largely because people *just don't write that code* - they put their declarations first, *then* their nested rules.) I don't think we should try to add more behavior for something that has proven itself to not be a problem in practice.
MQs wrap *all* naked properties in an `& {}`; style rules obviously *cannot* do this, so the behavior would be inconsistent either way. As the spec is currently written, style rules and MQs are each internally consistent with a single behavior for all naked properties. I think it would be a (probably minor) bad thing for style rules to have two behaviors, depending on relative ordering of rules and declarations.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1593800061 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 22:25:00 UTC