Definite max-block-size and auto block-size shouldn't establish a percentage basis
Categories
(Core :: Layout, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | unaffected |
firefox130 | --- | unaffected |
firefox131 | --- | unaffected |
firefox132 | --- | fixed |
People
(Reporter: TYLin, Assigned: TYLin)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
nsIFrame::ComputeBSizeValueAsPercentageBasis()
[1] incorrectly returns a definite percentage basis with a definite max-block-size and an auto block-size. We should only apply min-block-size & max-block-size constraint if block-size is a definite value.
Comment 1•2 months ago
|
||
Set release status flags based on info from the regressing bug 1909761
Assignee | ||
Comment 2•2 months ago
|
||
That is, a definite max block-size and an auto block-size should not compute a
definite percentage basis in the block axis.
Note that we accidentally pass
testing/web-platform/tests/css/css-sizing/intrinsic-percent-replaced-017.html
.
After applying this patch, the test starts to fail, but it will be fixed in the
next part.
Assignee | ||
Comment 3•2 months ago
|
||
In a column-oriented flex container, if a flex item's intrinsic inline size or
its descendants' inline size contributions depend on the item's block size,
NS_FRAME_DESCENDANT_INTRINSIC_ISIZE_DEPENDS_ON_BSIZE
will be set. In this
case, when determining the flex item's cross-size, we need to mark the flex
item's intrinsic inline size as dirty such that its (auto) inline size is
recomputed when constructing its ReflowInput
.
testing/web-platform/tests/css/css-sizing/intrinsic-percent-replaced-017.html
is the test coverage for this patch.
Comment 5•2 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e8d914658c03
https://hg.mozilla.org/mozilla-central/rev/51fd81b5ced0
Description
•