1350855 - [css-grid] CSS Grid Layout misbehaves with a min-height container

Status: RESOLVED DUPLICATE of bug 1346699

(Core :: Layout, defect)

Description

[david]

Attachment: actual.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170316213829

Steps to reproduce:

https://codepen.io/anon/pen/vxWMGJ

<style>
section  {
	min-height: 100vh;
	display: grid;
	grid-template-rows: auto auto 1fr auto;
}
</style>
<section>
 <article style='background:red'>AAA</article>
 <article style='background:green'>BBB</article>
 <article class="expand" style='background:blue'>CCC</article>
 <article style='background:orange'>DDD</article>
</section>



Actual results:

The third article has its intrinsic height, while the three others fill the remaining space.
The spec example https://www.w3.org/TR/css3-grid-layout/#adapting-to-available-space seems to imply this should work.
If you do height rather than min-height on the container it works. So there probably is something wrong with min-height.


Expected results:

the three other articles have their intrinsic heights, while the third one fills the remaining space. 
It works in Chrome. The spec example https://www.w3.org/TR/css3-grid-layout/#adapting-to-available-space seems to imply this should work.
If you do height rather than min-height on the container it works. So there probably is something wrong with min-height.

Comment 1

[david]

Attachment: expected.png

Comment 2

[Justin [:JW_SoftvisionQA]]

I can reproduce this issue on my machine  	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0

I have concluded that this issue has been around for some time now after running a mozregression.

Comment 3

[Mats Palmgren (inactive)]

Thanks for your bug report.  This was fixed some time ago in bug 1346699
and the fix will be released in Firefox 53 (in a matter of days I believe).

david, pre-release builds are available if you want to verify:
https://www.mozilla.org/en-US/firefox/channel/desktop/

Comment 4

[Mats Palmgren (inactive)]

(FTR, I did verify that backing out the fix for bug 1346699 locally in
my beta tree did break this testcase again.)