Closed Bug 1863796 Opened 11 months ago Closed 10 months ago

[wpt-sync] Sync PR 43029 - Test that lostpointercapture is not dispatched synchronously with node removal.

Categories

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

Product:
Core
Component:
DOM: Events
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
122 Branch
Tracking Flags:
Tracking Status
firefox122 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Robert Flack <flackr@chromium.org> wrote:

Test that lostpointercapture is not dispatched synchronously with node removal.

In https://github.com/w3c/pointerevents/issues/487 we clarified that pointer
capture is lost in the next process pending pointer capture update.

Bug:None
Change-Id: I5c8a511a06d9f522c29267c30ddc92fbec5e96fe
Reviewed-on: https://chromium-review.googlesource.com/5012975
WPT-Export-Revision: 8a1323b62f18b780cd27353e601ccbb10220848c

Component: web-platform-tests → DOM: Events
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f8600f5d3042 [wpt PR 43029] - Test lostpointercapture not dispatched synchronously with node removal, a=testonly
Test result changes from PR not available.
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1180967287a6 [wpt PR 43029] - Test lostpointercapture not dispatched synchronously with node removal, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/1180967287a6

Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox122: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.