Closed
Bug 1402657
Opened 7 years ago
Closed 7 years ago
movementX and movementY values are incorrect for pointermove event
Categories
(Core :: DOM: Events, defect, P2)
Core
DOM: Events
Tracking
()
RESOLVED
DUPLICATE
of bug 1400143
People
(Reporter: l.pmd, Assigned: stone)
References
Details
(Whiteboard: [parity-Chrome][parity-Edge])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.29 Safari/537.36 Steps to reproduce: 1. Go to https://jsfiddle.net/f98hqqg5/1/ with pointer events enabled (Nightly Win64). 2. Try drag the red bar or green area (test #1). 3. Change the 'pointermove' event handler to 'mousemove' and re-run the test. 4. Try drag the red bar or green area (test #2). Actual results: #1: The elements will disappear off into the void almost instantly. #2: The elements will follow your mouse cursor. Expected results: Both times the elements should have followed your mouse cursor.
Updated•7 years ago
|
Component: Untriaged → DOM: Events
Product: Firefox → Core
Comment 1•7 years ago
|
||
How does this affect websites? Should we be concerned about getting this fixed before we reach beta?
Flags: needinfo?(htsai)
Comment 2•7 years ago
|
||
Pointer events aren't enabled on beta. http://searchfox.org/mozilla-central/rev/8efd128b48cdae3a6c6862795ce618aa1ca1c0b4/modules/libpref/init/all.js#5142 Just blocking bug 822898 should be enough.
Flags: needinfo?(htsai)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → sshih
Since I reported this bug I think you've covered it with https://bugzilla.mozilla.org/show_bug.cgi?id=1400143#a1499410_559389
Flags: needinfo?(sshih)
Assignee | ||
Comment 4•7 years ago
|
||
(In reply to Luke from comment #3) > Since I reported this bug I think you've covered it with > https://bugzilla.mozilla.org/show_bug.cgi?id=1400143#a1499410_559389 Yes, it is and I forgot to clean this one. Thanks for the reminder.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(sshih)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•