Closed Bug 1849353 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41529 - Handle clipped overflow correctly in table fragmentation.

Categories

(Core :: Layout: Columns, task, P4)

task

Tracking

()

RESOLVED FIXED
119 Branch
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

Component: web-platform-tests → Layout: Columns
Product: Testing → Core

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

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/96ebba58e3a9 [wpt PR 41529] - Handle clipped overflow correctly in table fragmentation., a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in before you can comment on or make changes to this bug.