- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2022 23:51:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain] <container-name> in @container ambiguities`, and agreed to the following: * `RESOLVED: disallow 'not' as a container name` * `RESOLVED: 'none', 'not', 'and', and 'or' would be disallowed. Only a single name allowed in @container rule` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-contain] <container-name> in @container ambiguities<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/7203<br> <dael> miriam: The way we have container-name at the start of an @container rule can be confused currently with keyword not<br> <fantasai> +1 to disallowing not<br> <TabAtkins> +1 to disallow "not"<br> <dael> miriam: @container might start with either container-name or not. First part is to disallow 'not' as a container name<br> <jensimmons> +1 seems obvious to me<br> <dael> Rossen_: I see support<br> <dael> Rossen_: Should be straightforward. Other opinions? Or objections?<br> <dael> RESOLVED: disallow 'not' as a container name<br> <dael> miriam: Next part is a question. not clear if you can query multiple names in an @container rule and what happens if you did. and or or condition?<br> <dael> miriam: Container can have multiple names. You can say if you use multiple names you need both or all. Or say this or that. Or disallow multiple names<br> <dael> miriam: Sort of use cases of any of the above. And all can be handled by other naming conventions. no clear reason to go one way or another<br> <dael> miriam: Most obvious to me if we allow multiple names is they're allr equired<br> <Rossen_> ack fantasai<br> <dael> fantasai: I think ligit use cases for AND and OR so logical thing to do is apply bool syntax here. Might not want to do that b/c that's adding a lot. I suggest only 1 container name, disallow not, and, and or. Consider in the future if we want a more powerful syntax<br> <dael> Rossen_: Reserve the bool names for now, only allow 1 container name, and that gives us future extensibility for bool and multi naming<br> <dael> miriam: Makes sense to me<br> <dael> fantasai: miriam you mentioned about disallowing none?<br> <dael> miriam: So none can't be the name of a container. none as a container name just removes container names. I don't think need to explicitly disallow, but could clarify that<br> <dael> fantasai: Makes a difference as to if rule is invalidated. I lean toward invalidating it<br> <dael> miriam: 'none', 'not', 'and', and 'or' would be disallowed. Only a single name allowed in @container rule<br> <dael> Rossen_: Sounds like a good summary. Opinions or objections?<br> <dael> RESOLVED: 'none', 'not', 'and', and 'or' would be disallowed. Only a single name allowed in @container rule<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7203#issuecomment-1144257312 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 June 2022 23:51:55 UTC