Re: [csswg-drafts] [css-contain-3] container :/ size (#7142)

The CSS Working Group just discussed `container ;/ style`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> subtopic: container ;/ style<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7142<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7142<br>
&lt;fantasai> miriam: Wit the container shorthand, it takes 2 values, and because one of them accepts custom idents and other accepts keywords and hard to distinguish, we have a slash separator<br>
&lt;fantasai> miriam: at this point both are optional<br>
&lt;fantasai> miriam: so can get into situation where you can mek this frowny face in the property declaration syntax<br>
&lt;fantasai> miriam: he suggests it looks weird, unsure if it's an actual problem<br>
&lt;fantasai> miriam: one possibility is to make container-name required in the shorthand<br>
&lt;fantasai> miriam: the only reason to use the shorthand would be to set both<br>
&lt;fantasai> miriam: with it required, would have to set 'none' as container name if you want to not have a name<br>
&lt;fantasai> miriam: I don't feel strongly one way or another<br>
&lt;emilio> q+<br>
&lt;fantasai> miriam: we do want to encourage names, so ...<br>
&lt;TabAtkins> Fine with this, or we can fix the optionality by using the `[...]!` syntax in the grammar<br>
&lt;Rossen_> ack emilio<br>
&lt;fantasai> emilio: I see a very similar issue and what we're testing<br>
&lt;fantasai> emilio: what WPT is testing is container-type being mandatory and container-name being optional<br>
&lt;fantasai> emilio: why would you specify just the name?<br>
&lt;TabAtkins> (To resolve the "empty value becomes valid" problem raised.)<br>
&lt;fantasai> miriam: Right now we have default container-type of style on all elements<br>
&lt;fantasai> miriam: so that makes it optional<br>
&lt;fantasai> miriam: sometimes would just want to add a name to the style container<br>
&lt;fantasai> emilio: but shorthand expands to set container type to none<br>
&lt;fantasai> fantasai: we changed the initial value to style<br>
&lt;fantasai> Rossen_: seems we're running out of time here<br>
&lt;fantasai> Rossen_: not hearing any pushback on makign container name required, is it something we can resolve?<br>
&lt;fantasai> miriam: That's just for the shorthand syntax<br>
&lt;fantasai> emilio: ...<br>
&lt;fantasai> emilio: It makes sense to check what WPT tests are checking, optional name and required type<br>
&lt;fantasai> Rossen_: sounds we're not ready to resolve today<br>
&lt;fantasai> Rossen_: we'll end the call here, and recommend for posting opinions in issue<br>
&lt;fantasai> Rossen_: and we can bring it first thing next week<br>
&lt;emilio> ftr I filed https://github.com/w3c/csswg-drafts/issues/7180 yesterday<br>
</details>


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


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

Received on Wednesday, 30 March 2022 17:03:57 UTC