New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 621042 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Percent width on <img> incorrectly influences flex-basis resolution on its parent

Project Member Reported by dholb...@gmail.com, Jun 17 2016

Issue description

Version: Version 53.0.2767.4 dev (64-bit)
OS: Ubuntu 16.04

What steps will reproduce the problem?
(1) Load https://jsfiddle.net/4gnbt5L0/

What is the expected output?
  Small square image.

What do you see instead?
  Stretched wide image.

NOTES:
 - Firefox (50) and Edge (13) each give me "expected output". Chrome gives me the "instead" output.
 - The question here is, what should the flex-basis of the .item div be.  The .item has a single child, which has "width:100%" and an explicit pixel-valued height. Chrome incorrectly lets the "width:100%" on the img child to influence the width measurement, but it should not.  We should be measuring the max-content width of the flex item, and I think (?) the percent width on the child should not be resolvable against the available space in that measurement.
 - I believe the relevant spec text here is part "E" of https://drafts.csswg.org/css-flexbox-1/#algo-main-item  ("Determine the flex base size")
 

Comment 1 by e...@chromium.org, Jun 22 2016

Owner: cbiesin...@chromium.org
Status: Available (was: Untriaged)
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 22 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by e...@chromium.org, Jun 26 2017

Status: WontFix (was: Untriaged)
Now works as expected.
Status: Assigned (was: WontFix)
I still see it stretched? https://jsfiddle.net/4gnbt5L0/1/

Sign in to add a comment