New issue
Advanced search Search tips

Issue 782406 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Grid track does not stretch to height of scaled images

Reported by marcvang...@gmail.com, Nov 7 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Steps to reproduce the problem:
Test case: https://jsfiddle.net/5wdy33n0/5/

Situation: I created a layout with an auto-width grid column. A grid area which spans the top track contains images. Four images are styled to float left with a 25% width and auto height.

What is the expected behavior?
As the images scale and maintain their aspect ratio, they get higher. I expect the grid track to stretch in height, matching the height of the images inside. This does work in Firefox 56.

What went wrong?
The top grid track does not stretch in height to fit the auto-height images. Instead the grid track gets the height of the original, un-scaled image. For instance, when the images have a native size of 100px high, the grid track is also rendered at 100px high, even when the images are scaled up. The cause seems to be a combination of an auto-width grid column and stretched images.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 62.0.3202.75  Channel: stable
OS Version: Arch Linux 64
Flash Version: 

Also reported at https://github.com/rachelandrew/gridbugs/issues/27
 
chrome-grid-bug.html
1.2 KB View Download

Comment 1 by e...@chromium.org, Nov 8 2017

Cc: r...@igalia.com
Components: -Blink>Layout Blink>Layout>Grid

Comment 2 by e...@chromium.org, Nov 8 2017

Status: Available (was: Unconfirmed)
I confirmed the issue in 62.0.3202.62 but it seems it's already fixed in chrome 63.0.3239.9. I can do a bisect to figure out the specific patch that fixed the issue, though.

Comment 4 by r...@igalia.com, Nov 8 2017

Cc: svil...@igalia.com jfernan...@igalia.com
Status: WontFix (was: Available)
I didn't investigate it but I'm almost certain that this is the expected behavior in M62
(according to the spec at that moment), that was later fixed in M63 as the spec was modified.
The relevant CSS WG issues:
* https://github.com/w3c/csswg-drafts/issues/1117
* https://github.com/w3c/csswg-drafts/issues/1149

I think we can close this at this point.
Thanks you all for looking into this. I think you're right, those CSS WG issues are exactly the same problem. Sorry I didn't find those when I was investigating the problem. Good to know it has already been addressed.

Sign in to add a comment