- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Apr 2024 11:59:13 +0000
- To: public-css-archive@w3.org
@andruud It's not with the "intent to break it again later". It's with the intent to keep `@nest` as a better option than the "shifting up", but leaving the door open to explore other possibilities. > The specific changes we're discussing here can not necessarily be made later at all. If later on we prefer to switch to something else but it's not compatible, then so be it, we can stay with `@nest`. The point is that there was consensus that `@nest` is better than "shifting up". Exploring other possible approaches shouldn't block `@nest`, since delaying it will just make it not compatible. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2069212736 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 April 2024 11:59:14 UTC