1751896 - [wpt-sync] Sync PR 32529 - Disable fragment traversal correctly when block frag is enabled.

Status: RESOLVED FIXED

(Core :: Layout, task, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Sync web-platform-tests PR 32529 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/32529
Details from upstream follow.

Morten Stenshorne <[e-mail]> wrote:

Disable fragment traversal correctly when block frag is enabled.

Once we've entered legacy multicol, nothing inside should do fragment
traversal. The legacy multicol pre-paint code might create multiple
FragmentData entries for monolithic forced LayoutNG objects (such as
math and custom layout), because legacy layout doesn't really understand
what monolithic means.

This worked fine when LayoutNGBlockFragmentation was disabled, since
we'd always disable fragmentation inside multicol then. But when the
feature was enabled, we would allow fragment traversal of LayoutNG
subtrees inside legacy multicol. Don't do that.

Bug: 1289999
Change-Id: Iacddb22eb3df224ea57f988f37409bd57b5f200d
Reviewed-on: https://chromium-review.googlesource.com/3412124
WPT-Export-Revision: 8659249810bb5019bb04f096e4e340b660a1d2dc

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=f6da8af55dd5ff228c216e70a6409a646ca4c545

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, and Chrome on GitHub CI

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 1

Links

GitHub PR Head
GitHub PR Base

Comment 3

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/4445a9b5813d