- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Dec 2022 18:00:08 +0000
- To: public-css-archive@w3.org
As I mentioned in the call, it would be good to define what kind of "continued refinement" we are looking for and open separate issues. Some issues we've heard with option 3 are: 1. Some people suggest making `&` mandatory at all times. 2. Others want to go the opposite way, and make it optional in even more cases, this is what #7961 is about. 3. @plinss’s objection was related to how constraining this would be for future syntax; he is concerned that if anything that starts with a selector character is assumed to be a selector this will restrict future extensions significantly, and instead wants to limit what signifies that something is a nested rule. This to me sounds a lot like the previous nesting syntax, but perhaps there is another option. Peter, could you please open an issue so we can discuss? Is there something else we could refine? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8248#issuecomment-1361769179 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 December 2022 18:00:09 UTC