- From: Antti Koivisto via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 19:36:25 +0000
- To: public-css-archive@w3.org
Anything that references logical operators amounts to a new way of evaluating the query (remember there can be `or` on any level) or creates inconsistencies in nested queries. You could reasonably do > established as a valid query container for ~~all~~ **any** the container features without creating unnecessary complexity. Not sure that matches what you are after. In any case this feature has shipped and what is being proposed here is a potentially breaking behavior change. I'm not sure it has been justified sufficiently, or explained why it is safe to do. -- GitHub Notification of comment by anttijk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1372647616 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 19:36:27 UTC