Firefox and Chrome differ on whether to honor a definite width on an image descendant of a grid
Categories
(Core :: Layout: Grid, defect)
Tracking
()
Webcompat Priority | P3 |
People
(Reporter: twisniewski, Unassigned)
References
()
Details
Attachments
(1 file)
988 bytes,
text/html
|
Details |
In the attached test-case (reduced from the original webcompat.com report for Linode), Firefox appears to honor the width:710px
on the SVG image, while Chrome shrinks it. This causes an icon on Linode's page to appear much larger on Firefox.
Comment 1•4 years ago
|
||
FWIW:
(1) I don't see the bug on Linode's page - maybe they've already updated their markup to work around it? (I do see it in the attached testcase - thanks for creating that minimized testcase, Thomas!)
(2) If I add min-width:0
on the grid item here, then Firefox changes to match Chrome. So this is a disagreement about the computation of the automatic minimum width.
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 2•3 years ago
|
||
Just FYI :mats, this is affecting the mobile layout at https://goerdetselv.dk/materialer/soem-og-skruer/guide-til-traeskruer
I've posted my diagnosis at https://webcompat.com/issues/68533 , but the gist of it is that adding a min-width:0
to the grid items before the page's JS reads the clientWidths of the image gallery items, things appear to work properly.
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Comment 3•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE
.
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
AFAICT the testcase is now behaving the same in Chrome and Firefox. Should we close this as WFM (do we think that the Gecko bug was actually fixed?).
Comment 5•2 years ago
|
||
Yeah, mozregression indicates that this was fixed by Bug 1799111.
Description
•