Closed Bug 735553 Opened 8 years ago Closed 8 years ago

Touchend events have a timestamp of zero

Categories

(Firefox for Android :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 14

People

(Reporter: diagrammer, Assigned: wesj)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Build ID: 20101123123540

Steps to reproduce:

Test page:  http://www.apprisant.com/tab/ts.html

The test page prints timestamps from touchstart and touchend events in the box.


Actual results:

The timestamp appears to be in microseconds. A quick tap should be about 100 milliseconds.


Expected results:

Should be in milliseconds, as it is in other browsers and the spec.

Asus Transformer TFT101 tablet, Android 4 (ICS),
Firefox (11) Beta.
OS: Linux → Android
Hardware: x86 → Other
This is fixed in 13.0a1 (Native Fennec). Although, I am getting a timestamp of 0 for touchend events. I am going to repurpose this bug for that.
Attached patch PatchSplinter Review
We're taking the same path with both TOUCH_MOVE events and TOUCH_END events in nsPresShell.cpp. We create copies of the events there because (for TOUCH_MOVE at least) we have to dispatch them multiple times (its possible some widget code could send two points lifted at the same time, and we might have to dispatch each of those separately. The Android backend will not currently do that).

We are dropping information in the copy.
Assignee: nobody → wjohnston
Attachment #605836 - Flags: review?(bugs)
Summary: touch event timestamp is in microseconds, should be milliseconds → Touchend events have a timestamp of zero
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: Other → ARM
Attachment #605836 - Flags: review?(bugs) → review+
https://hg.mozilla.org/mozilla-central/rev/c6f23448ec62
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 14
Version: Firefox 11 → Trunk
You need to log in before you can comment on or make changes to this bug.