[wpt-sync] Sync PR 41529 - Handle clipped overflow correctly in table fragmentation.
Categories
(Core :: Layout: Columns, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox119 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 41529 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/41529
Details from upstream follow.
Morten Stenshorne <mstensho@chromium.org> wrote:
Handle clipped overflow correctly in table fragmentation.
When we reach the end of a fragmentable node that clips its overflow,
children do not contribute to additional fragmentainers past that point.
See kDisableFragmentation in NGBreakStatus and
RelayoutWithoutFragmentation() in NGLayoutAlgorithm for details.The table code didn't handle this correctly. Use
InvolvedInBlockFragmentation() instead of checking if block
fragmentation is active, so that we also handle cases where there's an
incoming break token, but no more fragmentation is to take place.Table captions need to be re-laid out when we're re-laying out without
fragmentation, so that we resume at the break tokens, instead of
starting from scratch.Bug: 1459623
Change-Id: I90281cc5dcc1225865daa6ac755534631753df41
Reviewed-on: https://chromium-review.googlesource.com/4793490
WPT-Export-Revision: 888c4beb705f836985db550e34469fe68fe15f2e
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Assignee | ||
Comment 3•1 year ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests
Status Summary
Firefox
PASS
: 1
Chrome
CRASH
: 1
Safari
PASS
: 1
Links
Comment 5•1 year ago
|
||
bugherder |
Description
•