I'll be completely honest here—I don't fully understand everything going on here. ¯\\\_(ツ)_/¯ I build _with_ CSS; I don't build CSS. ;) So all I can say is that I have a strong gut feeling that implementing native CSS nesting in a way that breaks the compatibility that SCSS currently has with pure CSS is a bad move. Yes, I know the onus is not on CSS to retain that compatibility. Regardless, I feel like intentionally breaking it (or allowing it to break) when there are other ways to implement things will actively disrupt a large portion of the web. I presume that for whatever reason, implementing native CSS nesting in the exact same way that SCSS already does it has been ruled out? -- GitHub Notification of comment by proimage Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-747066003 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Wednesday, 16 December 2020 21:58:39 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:24 UTC