- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Apr 2023 17:51:50 +0000
- To: public-css-archive@w3.org
I think these are pretty different situations in practice, tho. We add to the set of "things that can go before `@import`" super rarely -- in fact, we've only done it once, with `@layer`. On the other hand, we add new things that would qualify for nesting fairly regularly - we recently added `@scope`, and just resolved to add `@initial-name-tbd`. So the set of things that may or may not trigger "no more properties from here on" is regularly changed, presenting new hazards. Ultimately, the question is still - what are we trying to protect authors from? This sort of interleaving has been allowed in Sass and related tools for many years, with the exact same "pretend all the properties are together at the top" behavior, and never caused notable issues. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8738#issuecomment-1526098026 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 April 2023 17:51:51 UTC