New issue
Advanced search Search tips

Issue 691725 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 531783
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome incorrectly resolves "min-height:auto" to 0, on nested flex container, in quirks mode

Project Member Reported by dholb...@gmail.com, Feb 13 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Load https://dholbert.github.io/tests/flexbox/nested-flex-quirksmode-1.html

What is the expected result?
There should be a border around the text. (Both flex containers should be as tall as the text that they wrap.)

What happens instead?
There is no border around the text. (Both flex containers collapse to 0 height.)


Please use labels and text to provide additional information.
Notes:
 - Edge and Firefox give "expected result".
 - Chrome gives "expected result" IF I modify the testcase to add <!DOCTYPE html>.  So there's some special quirks-mode-only behavior coming into play here (which does not exist in Firefox or Edge).
 - Even though the testcase has "flex: 0" on the inner flex container, it's not actually asking for that container to have 0 height -- it should instead collapse to its min-height, which should be the content height (from the special "min-height:auto" behavior in Flexbox)
 

Comment 1 by dholb...@gmail.com, Feb 13 2017

Sorry, forgot to fill in version info:
Chrome version: Google Chrome	58.0.3004.3 (Official Build) dev (64-bit)
OS: Ubuntu 16.10 64-bit (Linux)

Also, FWIW, I'm filing this as a result of this tweet (though my testcase is a bit more reduced than the one referenced in the tweet):
  https://twitter.com/jlongster/status/831207825120563200

Comment 2 by e...@chromium.org, Feb 14 2017

Owner: cbiesin...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by dholb...@gmail.com, Oct 17 2017

Description: Show this description

Comment 4 by dholb...@gmail.com, Nov 6 2017

Possibly related to  bug 596743  -- though note that this bug's got a quirks-mode dependence.

Here's a reference case (with <!DOCTYPE html>), which gives the expected/correct rendering in Chrome:
https://dholbert.github.io/tests/flexbox/nested-flex-quirksmode-1-ref.html
Mergedinto: 531783
Status: Duplicate (was: Assigned)
Fairly sure this is a dup of bug 531783; we still have flex-basis be 0%
well a combination of that one and  bug 596743 

Sign in to add a comment