Open Bug 1308929 Opened 4 years ago Updated 4 years ago

Percentage max-width/height on orthogonal writing-mode images isn't compatible with Chrome


(Core :: Layout, defect, P4, minor)




Tracking Status
firefox52 --- affected


(Reporter: mats, Unassigned, NeedInfo)



(Keywords: testcase)


(1 file)

Attached file testcase
Background: bug 823483 and

It seems we're still not compatible with Chrome in some cases,
see the attached testcase.

It appears to me that Chrome only applies this special rule in
the image inline direction, and always does it in that direction
whether it's orthogonal to its parent or not.

Whereas Gecko applies it to the image axis that corresponds to
the parent's inline-axis.

Both UAs seems to have some bugs that makes it hard to compare.
First, take the Grid rendering in both UAs with a pinch of salt -
both implementations are buggy in this area.
The other examples looks reasonably correct in Chrome.
It seems Gecko doesn't implement [width,height]:min-content in
the block-axis yet, which I think explains some differences in
the block examples.
(The resolution here matters for the implementation of image Grid items.)
Blocks: 1218178
It seems flexbox performance is also different.
Can you attach the flexbox testcase please?
Flags: needinfo?(percyley)
You need to log in before you can comment on or make changes to this bug.