Closed Bug 1809346 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 37824 - Ensure changes to painted caret property state cause a full update

Categories

(Core :: DOM: Selection, task, P4)

task

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Philip Rogers <pdr@chromium.org> wrote:

Ensure changes to painted caret property state cause a full update

We have an optimization to do a fast "repaint-only" update when paint
chunks do not change state. If changes can affect layerization, a full
paint artifact compositor update is needed though. This patch fixes a
bug where the caret's clip could change without causing a full update.
Changes to property states for drag carets are likely to have the same
issue, so the entire property tree state is tracked in this patch.

Bug: 1402110
Change-Id: I4324edff5f5b5119f39074a67fbc536a9bd8301f

Reviewed-on: https://chromium-review.googlesource.com/4144277
WPT-Export-Revision: 406233ed31fa3af1d05221fa4a6c71615d5d3a30

Component: web-platform-tests → DOM: Selection
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 9 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/3ae0f06fa84b [wpt PR 37824] - Ensure changes to painted caret property state cause a full update, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.