Closed Bug 1480580 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 12285 - Send click event to the nearest common ancestor

Categories

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

Product:
Core
Component:
DOM: Events
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12285 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/12285 Details from upstream follow. Navid Zolghadr <nzolghadr@chromium.org> wrote: > Send click event to the nearest common ancestor > > Send click event even when the targets of down and up > are different and across different interactive elements. > > Bug: 869919 > Change-Id: Ie90c2d7c7dbb1b873f2a0f8b8ef489ee951489fe > Reviewed-on: https://chromium-review.googlesource.com/1161164 > WPT-Export-Revision: 217934db671cca28fc31926b6d8558bf5c7c355c
Component: web-platform-tests → DOM: Events
Product: Testing → Core
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/9b7e3c0e4c3f [wpt PR 12285] - Send click event to the nearest common ancestor, a=testonly
https://hg.mozilla.org/mozilla-central/rev/9b7e3c0e4c3f
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.