- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Mar 2023 20:34:17 +0000
- To: public-css-archive@w3.org
> The same is true for sass. > Any argument goes both ways here :) Somewhat. Sass far predates CSS Nesting, and we're invading the same syntax space. This is different from projects that intentionally followed our spec, intending to match what browsers eventually ship with - there was always the chance that the spec changes before browsers ship. (It's already happened once, with the removal of `@nest` and loosening of restrictions on selectors. Anyone using `@nest` in those processors was "broken" to the exact same degree that anyone using `&div` today would be.) One must also realistically consider the scale of the userbases between the projects. We're talking compat here, so actual number-of-devs-affected is more than a theoretical concern. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8662#issuecomment-1490915615 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 March 2023 20:34:18 UTC