- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 May 2018 22:21:48 +0000
- To: public-css-archive@w3.org
> So the base sizes of the tracks should be 0 auto 0 @fantasai that statement makes no sense. Base sizes are the result from the Track Sizing Algorithm - they can't be "auto". They are always a definite size. I'm assuming you mean "the block-size of the grid item after it is flowed in a containing block (CB) that has an inline size of 200px". So, I assume you mean "0 ~200px 0". Also, I don't understand why you think the base size should be zero in the third test. You are correct that [Automatic Minimum Size](https://drafts.csswg.org/css-grid/#min-size-auto) doesn't apply, but that doesn't make the min-content contribution zero - it's still "the block-size after flowing it", which in this case is 204px (the CB inline size is definite (200px), which makes the `<figure>` width 200px which provides a CB inline size for the image which becomes 200px in height, which makes the `<figure>` grid item have block-size 204px in Nightly because the `<figure>` (a block) baseline adds 4px (adding `vertical-align:top` makes it 200px). I can't find any spec that says that `overflow != visible` (and a block-size that "behaves as auto") on non-replaced blocks implies they have zero min-content contribution. Please point it out if I missed it, thanks. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2674#issuecomment-390032497 using your GitHub account
Received on Thursday, 17 May 2018 22:21:54 UTC