mozMovementX is transient and becomes zero later

RESOLVED FIXED in Firefox 14



7 years ago
7 years ago


(Reporter: azakai, Assigned: humph)


(Blocks 1 bug)

Dependency tree / graph
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(firefox14+ fixed)



(2 attachments, 1 obsolete attachment)



7 years ago
Posted file testcase
mousemove events have valid mozMovementX and Y values, but if that event object is saved somewhere and processed later, the value of mozMovementX is 0. This is quite surprising and a problem for web pages that want to process the event info later.

For example, if you receive such an event and do a setTimeout whose closure captures the event, the timeout will print 0 for mozMovementX.

The attached testcase shows this, search for 'zz' to see the relevant lines. Looking in the web console it is clear mozMovementX is valid when received, but zero'd out later.


7 years ago
nsDOMUIEvent::DuplicatePrivateData() should handle also movementX/Y
This is a bug in the newly implemented Mouse Lock API. Tracking for FF14.

Comment 3

7 years ago
As an aside, this test case is triggering bug 731350 for me when I go fullscreen.
Assignee: nobody → david.humphrey

Comment 4

7 years ago
Posted patch Patch v1 (obsolete) — Splinter Review
Attachment #620296 - Flags: review?(bugs)
Attachment #620296 - Flags: review?(bugs) → review+
seems like there's a rash of tracking flags being reset going around.  fixing. we're tracking this for 14.

Comment 6

7 years ago
I wanted to run this through try server before updating, but now that I've done that, this looks good.
Attachment #620296 - Attachment is obsolete: true
Attachment #622237 - Flags: review+


7 years ago
Keywords: checkin-needed
Version: unspecified → Trunk

Should this have an automated test?
Flags: in-testsuite?
Keywords: checkin-needed
Target Milestone: --- → mozilla15
Last Resolved: 7 years ago
Resolution: --- → FIXED
Please nominate for Aurora approval so we can uplift.
Comment on attachment 622237 [details] [diff] [review]
Patch v2 (r=smaug)

[Approval Request Comment]
Bug caused by (feature/regressing bug #): NA
User impact if declined: buggy behavior in certain cases
Testing completed (on m-c, etc.): in m-c about a month
Risk to taking this patch (and alternatives if risky): very low risk 
String or UUID changes made by this patch: NA
Attachment #622237 - Flags: approval-mozilla-beta?
Comment on attachment 622237 [details] [diff] [review]
Patch v2 (r=smaug)

[Triage Comment]
Low risk fix for new feature. Approved for Beta 14.
Attachment #622237 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.