Closed Bug 1849574 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41557 - Locate parent fragment of nested OOF multicol correctly.

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 41557 into mozilla-central (this bug is closed when the sync is complete).

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Locate parent fragment of nested OOF multicol correctly.

The code didn't sufficiently examine the containing block chain. We need
to locate the nearest non-out-of-flow containing block that has a
non-out-of-flow fragmentation context root as its containing block
(unless the fragmentation context root is the LayoutView (printing),
which is hard-coded as absolutely positioned) - and then place the new
fragment under this fragmentation context root. This is what the
fragment tree looks like, so, when replacing a fragment after OOF
layout, it needs to behave exactly the same, or we'll find to find the
old fragment in the fragment tree.

Bug: 1459154
Change-Id: I0a3ae3ea07331db13566883f98dee3f1a989e5c4
Reviewed-on: https://chromium-review.googlesource.com/4798090
WPT-Export-Revision: 5ef2e8a9819f534268ed055944b50f7d3da88406

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

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e3a4f13ebd9e [wpt PR 41557] - Locate parent fragment of nested OOF multicol correctly., 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.