Closed Bug 1827927 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 39525 - Pre-paint: Match OOF layout behavior inside clipped containers.

Categories

(Core :: Layout, task, P4)

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Pre-paint: Match OOF layout behavior inside clipped containers.

An OOF fragment is normally a direct child of a fragmentainer - unless
it's inside something monolithic. However, we need to check if this is
something truly monolithic, and not just a fragment that was set as
monolithic because we reached the end of a clipped container; see
NGConstrinatSpace::DisableFurtherFragmentation().

Otherwise we'd end up in PrePaintTreeWalk::WalkMissedChildren()
needlessly, and ignore any clipping.

Bug: 1432946
Change-Id: I24fc774f40bf337419f7e6ec336101e00a856f8a
Reviewed-on: https://chromium-review.googlesource.com/4422851
WPT-Export-Revision: bf05d47b747d72aaf45f6cae196a1e05339d1f70

Component: web-platform-tests → Layout
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

CI Results

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

Total 3 tests

Status Summary

Firefox

PASS: 3

Chrome

FAIL: 3

Safari

PASS: 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/50c19c23a196 [wpt PR 39525] - Pre-paint: Match OOF layout behavior inside clipped containers., a=testonly
Status: REOPENED → RESOLVED
Closed: 3 years ago3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.