Closed Bug 1675430 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 26407 - element.click does not fire PointerEvent when ClicPointerEvent enabled

Categories

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

Product:
Core
Component:
DOM: Events
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
85 Branch
Tracking Flags:
Tracking Status
firefox85 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Liviu Tinta <liviutinta@chromium.org>' wrote:

element.click does not fire PointerEvent when ClicPointerEvent enabled

As part of changing click, auxclick and contextmenu into PointerEvent,
element.click() needs to fire a click PointerEvent instead of a
click MouseEvent.

Bug: 989958
Change-Id: I55bebd436f04f6b54cdccb1954a9299a3ede9c8c
Reviewed-on: https://chromium-review.googlesource.com/2520239
WPT-Export-Revision: 11660905e7a777cc1a0b10477b03e3808c940487

Component: web-platform-tests → DOM: Events
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/uievents/interface/click-event.htm
synthetic click event is a PointerEvent: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2e189267b9d0
[wpt PR 26407] - element.click should fire a PointerEvent when ClickPointerEvent enabled, a=testonly
https://hg.mozilla.org/integration/autoland/rev/df732331dc5b
[wpt PR 26407] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/2e189267b9d0
https://hg.mozilla.org/mozilla-central/rev/df732331dc5b

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox85: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in before you can comment on or make changes to this bug.