Closed Bug 1847527 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41360 - Avoid marking ancestor layout objects during pre-paint.

Categories

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

task

Tracking

()

RESOLVED FIXED
118 Branch
Tracking Status
firefox118 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Morten Stenshorne <mstensho@chromium.org> wrote:

Avoid marking ancestor layout objects during pre-paint.

If we really need to mark an object for paint invalidation checking
during pre-paint, stay away from the ancestors, since we might already
be done with them, and therefore end up leaving them dirty "forever".

Even if they are ancestors, LayoutObject-tree-wise, it doesn't have to
mean that are ancestors in the physical fragment tree.

Bug: 1451185
Change-Id: I9fef344619cfe6a99d80dd49e904fd41dd464167
Reviewed-on: https://chromium-review.googlesource.com/4755525
WPT-Export-Revision: b5bef607936be1d8eb20a62c2f5d0570a81b90f6

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

PASS: 1

Safari

PASS: 1

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3ff2e523658d [wpt PR 41360] - Avoid marking ancestor layout objects during pre-paint., a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in before you can comment on or make changes to this bug.