Closed
Bug 1564710
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 17614 - Move a pointercapture pointer test to non-wpt pointerevent tests.
Categories
(Testing :: web-platform-tests, task, P4)
Testing
web-platform-tests
Tracking
(firefox70 fixed)
RESOLVED
FIXED
mozilla70
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 17614 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/17614
Details from upstream follow.
Ella Ge <eirage@chromium.org> wrote:
Move a pointercapture pointer test to non-wpt pointerevent tests.
This test initially added to wpt but the behavior is not clearly defined
in spec. So move to non-wpt pointerevents test.
See discussion in https://github.com/w3c/pointerevents/issues/291Change-Id: Ic871c57526681d790d6e68081f5a4bf8316e8494
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1684464
Reviewed-by: Ella Ge \<eirage@chromium.org>
Commit-Queue: Ella Ge \<eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#674191}
| Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Updated•6 years ago
|
Type: -- → task
| Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Assignee | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Assignee | ||
Comment 1•6 years ago
|
||
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/05b8c92a2d89
[wpt PR 17614] - Move a pointercapture pointer test to non-wpt pointerevent tests., a=testonly
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in
before you can comment on or make changes to this bug.
Description
•