Closed Bug 1323400 Opened 3 years ago Closed 6 months ago

[PointerEvents] Long taps keeps firing the "pointermove"


(Core :: DOM: Events, defect, P3)

53 Branch
Windows 10



Tracking Status
firefox53 --- wontfix
firefox67 --- fixed


(Reporter: cynthiatang, Assigned: edgar)


(Blocks 4 open bugs)



(4 files)

Steps to reproduce:
 1. Launch Firefox with Pointer Events
 2. Open 
 3. Long tap in an empty area

Expected result:
 - pointerType="touch"

Actual result:
 - pointerType="touch"
 - But it keeps firing the "pointermove" 
 - Videos:
    - Enable pointerEvents:
    - Disable pointerEvents:

 - Devices: Surface 3
 - OS: Windows 10 Pro. (64bit)
 - Firefox:53.0a1 (2016-11-30) (64-bit)
Priority: -- → P2
Without export MOZ_USE_XINPUT2=1, OS keeps firing mousemove and then we generates pointermove from those mousemove events.

As I know, the touch functionality is not working w/o export MOZ_USE_XINPUT2=1. And there are some bugs with MOZ_USE_XINPUT2=1.
Moving to p3 because no activity for at least 1 year(s).
See for more information
Priority: P2 → P3
The bug was reported on windows; however comment 1 confusingly indicated a linux configuration. Worth checking it again.
Blocks: pointerevent

I could reproduce it on Windows Surface, pointermove event keeps being fired even if the touch isn't moved.

TouchManager will filter out the duplicated events if the touch isn't changed, And the pointer event seems doesn't handle this well.

Blocks: 1505321
Blocks: 1315250
Assignee: stone123456 → echen

To make it easier to add new test without introudcing duplicated code.

Pushed by
Part 1: Mark Touch::Equals as a const method; r=smaug
Part 2: Filter out duplicated touchmove for pointer event; r=smaug
Part 3-1: Refactor test_multiple_touches.html; r=smaug
Part 3-2: Add test; r=smaug
Blocks: 1523998
You need to log in before you can comment on or make changes to this bug.