- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 May 2024 18:02:04 +0000
- To: public-css-archive@w3.org
The objection from WebKit is that `@nest {}` doesn't have a purpose other than fixing this wart. `@group {}` ultimately has the same issue unless we already commit to giving it a purpose later. I am not sure we should be designing new syntax in this order.
In this way I also agree with @tabatkins when they said:
> We can also make the name much less attractive and more obviously internal, if that would help, like `@implicit-nested-properties-group {...}` or something. Slightly on the ridiculous side for length, so it's not something an author would ever reach for when writing code manually, but also a very descriptive name that suggests what it's doing immediately, and is much easier to google for.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2133892524 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 May 2024 18:02:05 UTC