Re: [csswg-drafts] [css-contain] specified column/row sizes on grid containers should contribute to contain:size

The Working Group just discussed `Contain`, and agreed to the following:

* `RESOLVED: No change, add a note.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Contain<br>
&lt;Rossen> github:https://github.com/w3c/csswg-drafts/issues/2804<br>
&lt;fantasai> florian: When you apply size containment, we first lay out the element as if it's empty<br>
&lt;fantasai> florian: And then put content into it<br>
&lt;fantasai> florian: Your'e expected to give it a size<br>
&lt;fantasai> florian: Question: for a grid containe,r which has rows and columns of fixed size<br>
&lt;fantasai> florian: Even if element was empty, it would have a non-zero size<br>
&lt;fantasai> florian: That's not how it's implemented atm<br>
&lt;fantasai> florian: Currently asssumed to have zero size, even if 6 100px columns<br>
&lt;fantasai> florian: We have same similar issue with multicol<br>
&lt;fantasai> florian: Spec currently say that empty columns and grid rows should help auto-sized size-contained element not be zero<br>
&lt;fantasai> florian: But #1 chrome isn't doing that and #2 fixing in inline direction, but in block direction wouldn't be easy<br>
&lt;fantasai> florian: Because no codepath to get vertical intrinsic size without doing layout<br>
&lt;fantasai> TabAtkins: I don't care a ton, if really problematic, but in general the idea is to "lay out as if empty" and for a grid, that means we make it the height of the fixed-height rows<br>
&lt;fantasai> florian: If we remove it nothing's destroyed, just maybe a bit inconvnient<br>
&lt;fantasai> ericwilligers: Isn't purpose of contain that author provides the size?<br>
&lt;fantasai> florian: Author gave us the info, though 6 100px columns plus a gap, simple math the author could do, by we could also do<br>
&lt;fantasai> TabAtkins: min-height is handled, why not sum of row heights<br>
&lt;fantasai> ...<br>
&lt;fantasai> florian: On Chrome side, Igalia would be fixing it. They would do it, but want to make sure we want it.<br>
&lt;fantasai> heycam: In the original filed issue, Morgan suggested that it should work. So I think that would be Mozilla's position<br>
&lt;fantasai> florian: I can add a note to the spec, to make sure it's not forgotten<br>
&lt;fantasai> RESOLVED: No change, add a note.<br>
</details>


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

Received on Thursday, 5 July 2018 00:04:23 UTC