- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Apr 2022 16:06:45 +0000
- To: public-css-archive@w3.org
- I agree, we should disallow `not` as a `<container-name>` - I don't think we want `none` in the `@container <name>` syntax, so should probably clarify that production either way. I would lean towards allowing multiple names in a query, and defining them to act as a combined filter, so that a container for your query would have to match both `foo` AND `bar` names. It's more important that we allow multiple names on a container itself (the property), but given that containers may have multiple names, it seems useful that you could be more explicit about combinations of names that need to be present for a query. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7203#issuecomment-1091922630 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 April 2022 16:06:46 UTC