Closed Bug 1532197 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 15605 - WPT test for touchmove event listener passive by default intervention.

Categories

(Core :: DOM: Core & HTML, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Sahel Sharify <sahel@chromium.org> wrote:

WPT test for touchmove event listener passive by default intervention.

This cl adds WPT for touchmove event listener and modifies the existing
wpt test for the wheel event listener intervention. These tests pass only
when threaded compositing is enabled and that's why I have marked them as
Skip in test expectations, until --enable-threaded-compositing is enabled
for WPT tests by default (see issue 770028) I wrote the equivalent versions
of the tests using gpubenchmarking in fast/scrolling so that they run in
virtual/threaded test suite.

Bug:936891, 626196
Change-Id: I9e96736b9fbe7394d2c8157d2120457976a1d812
Reviewed-on: https://chromium-review.googlesource.com/1495437
WPT-Export-Revision: 31feaa0f7f1310016cb960cf5f92730661ec441c

Component: web-platform-tests → DOM
Product: Testing → Core
Ran 1 tests ERROR : 1 New tests that have failures or other problems: /dom/events/document-level-touchmove-event-listener-passive-by-default.html: ERROR
Component: DOM → DOM: Core & HTML
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/4533b02dac5b [wpt PR 15605] - WPT test for touchmove event listener passive by default intervention., a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/f8af97df3e34 [wpt PR 15605] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.