Closed Bug 1742846 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 31734 - Invalidate paint when CompositingContainer changes

Categories

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

task

Tracking

()

RESOLVED FIXED
96 Branch
Tracking Status
firefox96 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Philip Rogers <pdr@chromium.org> wrote:

Invalidate paint when CompositingContainer changes

PaintLayer::CompositingContainer may change when stacking changes. We
mark the previous compositing container for repaint in
|LayoutBoxModelObject::StyleWillChange| but also need to mark the new
compositing container chain for repaint.

Bug: 1271871
Change-Id: Ief05ea5c26ae27ebe2918db293ad8e17a5851a9a
Reviewed-on: https://chromium-review.googlesource.com/3300510
WPT-Export-Revision: 828a2bb94846738c6b22e8fa9516ffdb55db744c

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

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

FAIL: 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/f33a851e0a6e
[wpt PR 31734] - Invalidate paint when CompositingContainer changes, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in before you can comment on or make changes to this bug.