Closed Bug 1813926 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 38270 - Check if an object is in a locked display before executing update.

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox111 fixed)

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Yotam Hacohen <yotha@chromium.org> wrote:

Check if an object is in a locked display before executing update.

When we walk the tree in pre-paint, we stop the walk for children of an
object with locked display. This patch adds a similar check to the
deferred updates that are executed separately after the walk.

Bug: 1407382
Change-Id: I00c8b73eab7d9101882f264191d25f04c8158cb1
Reviewed-on: https://chromium-review.googlesource.com/4189343
WPT-Export-Revision: 49623893443bef0f01f6d5c8612a963eb87a084d

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/f942d0cc34de
[wpt PR 38270] - Check if an object is in a locked display before executing update., a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.