Closed
Bug 1830192
Opened 2 years ago
Closed 2 years ago
Auto-height block container wrongly draws block-end border with max-height constraint
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
RESOLVED
FIXED
115 Branch
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: TYLin, Assigned: TYLin)
References
Details
Attachments
(1 file)
See the last subtest of Bug 1828977 testcase 2.
Quote Daniel's observation in bug 1828977 comment 4:
Firefox unnecessarily (?) draws a thin strip of the container in the second column, followed by the border-bottom in the 3rd column.
Assignee | ||
Comment 1•2 years ago
|
||
Nowadays BlockReflowState::BorderPadding()
won't skip the block-end border and
padding [1] because we use PreReflowBlockLevelLogicalSkipSides()
which always
assume the current fragment is the last fragment. Therefore, This change removes
the note and retrieve block-end BP directly from borderPadding
, which is an
alias of BlockReflowState::BorderPadding()
.
The only difference between the added test and reference file are height
and
max-height
, so the test verifies the fragmentation are consistent internally.
Pushed by aethanyc@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/df519de7261a
Fix fragmentation for blocks with auto height and fixed max-height. r=dholbert
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/39917 for changes under testing/web-platform/tests
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox115:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•