Closed Bug 1866572 Opened 10 months ago Closed 9 months ago

[wpt-sync] Sync PR 43344 - Lose pointer capture if capture target is removed by gotpointercapture.

Categories

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

task

Tracking

()

RESOLVED FIXED
123 Branch
Tracking Status
firefox123 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Robert Flack <flackr@chromium.org> wrote:

Lose pointer capture if capture target is removed by gotpointercapture.

Also check that capture target is still in DOM before getting pointer capture.

Bug:1502031
Change-Id: Id7791dbd01fc8b688a23120dc4bdeec8e6bf62f8
Reviewed-on: https://chromium-review.googlesource.com/5053186
WPT-Export-Revision: 5d6672c59a3be7658a3df6bb9f1defc205e62144

Component: web-platform-tests → DOM: Events
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bf87d67abfd1 [wpt PR 43344] - Lose pointer capture if capture target is removed by gotpointercapture., a=testonly https://hg.mozilla.org/integration/autoland/rev/e68772ddb362 [wpt PR 43344] - Update wpt metadata, a=testonly
Test result changes from PR not available.
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/8c080914f56d [wpt PR 43344] - Lose pointer capture if capture target is removed by gotpointercapture., a=testonly https://hg.mozilla.org/integration/autoland/rev/d128effa7249 [wpt PR 43344] - Update wpt metadata, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in before you can comment on or make changes to this bug.