W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2016

Re: [csswg-drafts] [css-grid] Implied Minimum Size of Grid Items

From: Manuel Rego Casasnovas via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Nov 2016 12:50:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-262769354-1479991827-sysbot+gh@w3.org>
And now thinking again about [2) from my previous 
comment](https://github.com/w3c/csswg-drafts/issues/283#issuecomment-262481269).

```html
  <div style="display: inline-grid; width: 40px; height: 40px; grid: 
minmax(0px, auto) / minmax(0px, auto); border: thick solid; font: 
100px/1 Monospace;">
    <div style="background: magenta;">item</div>
  </div>
```

A) If instead of `minmax(0px, auto)` we use `minmax(0px, 500px)`, both
 browsers agree that the item should be 40x40:
![40x40 
item](https://cloud.githubusercontent.com/assets/11602/20598954/e57ba2c0-b24b-11e6-9bf7-baa181c749ef.png)

B) So, if we use `minmax(0px, auto)` and `auto` is bigger than 40px 
(let's say 250px), I believe we should still behave the same and the 
item should still be 40x40.

C) However if the track is only `auto`, then is when the minimum size 
plays its role and causes it to be bigger (250px) and overflow the 
grid container.

![Bigger 
item](https://cloud.githubusercontent.com/assets/11602/20599044/64675494-b24c-11e6-91d7-018c03b605f6.png)

This is related to the step of the alogrithm in which we maximize the 
track sizes, as the free space would be only the 40px of the grid 
container.

Note that in these examples Firefox and Chromium have the same 
behavior for A) and C) but not for B).


-- 
GitHub Notification of comment by mrego
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/283#issuecomment-262769354 
using your GitHub account
Received on Thursday, 24 November 2016 12:50:35 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:05 UTC