| commit | 0cfbb3b5ba802826f1ce88fbb6f5b0eb5e767c4d | |
| author | James Graham <james@hoppipolla.co.uk> | |
| Tue, 12 Jul 2022 12:00:30 +0000 (12 12:00 +0000) | ||
| committer | James Graham <james@hoppipolla.co.uk> | |
| Tue, 12 Jul 2022 12:00:30 +0000 (12 12:00 +0000) | ||
| tree | 621145452cfecc8acd6b63c2f1729af619bdc017 | treesnapshot (tar.gz zip) |
| parent | fa529a01f62ddb6e75725f76142d44c6c553b5bb | commitdiff |
Bug 1543337 - Allow multiple pointermove events in touch infrastructure tests, r=webdriver-reviewers,whimboo
At least in gecko, we are generating a pointermove event for each
pointer even when there was no actual change. This corresponds to the
behaviour of touch events, where the touchmove event includes all
active touch points.
Although this looks like it doesn't match the intent of the Pointer
Events spec, for an infrastructure test that's just checking if the
testdriver feature is supported, it seems better to allow the
discrepancy from the ideal behaviour rather than imply that the whole
feature is broken.
Differential Revision: https://phabricator.services.mozilla.com/D151276
At least in gecko, we are generating a pointermove event for each
pointer even when there was no actual change. This corresponds to the
behaviour of touch events, where the touchmove event includes all
active touch points.
Although this looks like it doesn't match the intent of the Pointer
Events spec, for an infrastructure test that's just checking if the
testdriver feature is supported, it seems better to allow the
discrepancy from the ideal behaviour rather than imply that the whole
feature is broken.
Differential Revision: https://phabricator.services.mozilla.com/D151276