Open Bug 1677616 Opened 4 years ago Updated 4 years ago

The size of ratio-determining axis should be the value before applying min/max constraints

Categories

(Core :: Layout, defect, P3)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

People

(Reporter: boris, Unassigned)

References

(
URL
)

Details

Based on the current spec ISSUE 6:

The resolved preferred size in the ratio-determining axis (before applying min/max) gets transferred thru the ratio. Min/max constraints get transferred afterwards, and then applied to each axis independently without regards to aspect-ratio.

This means the inline size we used to compute the block size through aspect-ratio should be the value before applying min/max constraints. Now, if the ratio-determining axis is inline axis, we use the incorrect size to compute the block size through aspect-ratio. (code)

We probably need to start to think: should we merge the implementation of nsIFrame::ComputeSize and nsContainerFrame::ComputeSizeWithIntrinsicDimensions

Summary: The size of ratio-determining axis should be before applying min/max. → The size of ratio-determining axis should be the value before applying min/max constraints

OK, this may not be an issue because we implicitly apply the transferred min/max size constraints on the transferred preferred block size if we keep our current implementation. Just leave this bug for tracking this potential issue.

You need to log in before you can comment on or make changes to this bug.