- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 06:59:25 +0000
- To: public-css-archive@w3.org
Can we split up this proposal in multiple threads? Too much is being lost because everyone focuses on one ore two details of the previous statement. It is not easy to discuss the core of this proposal without getting stuck discussing the side effects. I see these parts, but maybe there are more: - a parser switch mechanic and if this is the best thing for the language - the exact syntax/chars that trigger this parser switch - relative selector syntax in nested contexts - copy-paste between contexts Descendant operator being an implicit default when `&` is missing is not in this list because it is a side effect of having relative selector syntax and a parser switch mechanic. Things like the parser switch mechanic need to researched in detail because it is something we can not take back, it will change language fundamentally. A separate thread is more suitable in my opinion. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1274175805 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 06:59:27 UTC