Re: [csswg-drafts] [css-contain-3] Move style() to the feature level in the grammar (#7073)

The CSS Working Group just discussed `[css-contain-3] Move style() to the feature level in the grammar`, and agreed to the following:

* `RESOLVED: Keep the current behavior`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-contain-3] Move style() to the feature level in the grammar<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/7073<br>
&lt;dael> miriam: When we defined both size and style functions for the @container rule we made them so they could wrap larger chunks of syntax so can have multiple style queries in style<br>
&lt;dael> miriam: Seemed useful as syntax sugar. Since then removed size and left only with style and possibility of future functions<br>
&lt;dael> miriam: What we're looking at is do we still want style and any future functions to have that sugar of allowing multiple queries or statements inside the function? Or restrict to each function is a query?<br>
&lt;dael> miriam: Provided 2 examples, don't look terribly different. Lean slightly toward keeping flexibility but very slight. Anders argued to remove it<br>
&lt;Rossen_> ack fantasai<br>
&lt;dael> fantasai: My thought is that it's annoying to type something over and over again. If you have a complex style query it would be annoying to type style again and again. Syntax has built in logic to handle multiple. I think for author friendliness it's better to allow<br>
&lt;fantasai> s/Syntax has/Selectors has/<br>
&lt;dael> Rossen_: If Anders is not here; anyone in favor of dropping?<br>
&lt;fantasai> s/multiple/multiple boolenan logic/<br>
&lt;dael> miriam: I haven't heard from anyone else in that direction<br>
&lt;dael> Rossen_: I'm fine with taking a resolution and revisiting in case Anders has a strong position and reason. From listening to WG seems we're leaning more to keep it<br>
&lt;dael> Rossen_: Other opinions?<br>
&lt;dael> Rossen_: Objections to keep the current behavior?<br>
&lt;dael> RESOLVED: Keep the current behavior<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7073#issuecomment-1057531660 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 3 March 2022 00:18:26 UTC