- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Mon, 11 Apr 2016 16:58:45 -0400
- To: Sergio Villar Senin <svillar@igalia.com>, www-style list <www-style@w3.org>
On 03/30/2016 05:13 AM, Sergio Villar Senin wrote: > Hi, > > another doubt regarding how to compute the size of auto tracks. Specs > literally say: > > "For auto minimums: If the track has an auto min track sizing function > and the grid container is being sized under a min/max-content > constraint, set the track’s base size to the maximum of its items’ > min/max-content contributions, respectively. > Otherwise, set its base size to the maximum of its items’ “min-size > contributions”: the value specified by its respective min-width or > min-height properties (whichever matches the relevant axis) if the > specified size is auto, or else the item’s min-content contribution." > > So we either return the min|max-content contribution or the value > specified for the correspondent min-size property. In the case of > min|max-content contribution is pretty clear from the definition[1] that > we should include border, padding and margin. But in the case of > returning the value specified by min-height|width the specs does not say > anything. In Blink/WebKit we're adding them too in that case just for > coherency with the other case, but wanted to double check it with the > working group. Yeah, we forgot to mention that it's the outer size we're interested in. Fixed in https://hg.csswg.org/drafts/diff/dc3737661a44/css-grid/Overview.bs > BTW we're always using items' border, paddings and margins to compute > the sizes of content-sized tracks (or when computing alignment). That is > not explicitly mentioned in the specs either but I guess is the right > thing to do. Isn't it? Yes. The min/max-content size contributions are defined to be outer sizes. ~fantasai
Received on Monday, 11 April 2016 20:59:15 UTC