Closed
Bug 780318
Opened 12 years ago
Closed 12 years ago
createEvent("touchevent"),timeStamp is in microseconds instead of milliseconds
Categories
(Core :: DOM: Events, defect)
Tracking
()
People
(Reporter: eeejay, Unassigned)
Details
Attachments
(1 file)
924 bytes,
patch
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•12 years ago
|
||
Attachment #648907 -
Flags: review?(wjohnston)
Comment 2•12 years ago
|
||
Comment on attachment 648907 [details] [diff] [review] Initialize touch events with millisecond timestamps Smaug should look at this.
Attachment #648907 -
Flags: review?(wjohnston) → review?(bugs)
Comment 3•12 years ago
|
||
We have an old bug open to fix timestamps in all the events.
Comment 4•12 years ago
|
||
Comment on attachment 648907 [details] [diff] [review] Initialize touch events with millisecond timestamps Since there is no explanation why this needs to be fixed now specifically for touch events, cancelling review.
Attachment #648907 -
Flags: review?(bugs)
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #3) > We have an old bug open to fix timestamps in all the events. What is the bug #? Can't we either mark this as a dup, or make it a dependant on the other bug? What is the downside of landing this patch? (In reply to Olli Pettay [:smaug] from comment #4) > Comment on attachment 648907 [details] [diff] [review] > Initialize touch events with millisecond timestamps > > Since there is no explanation why this needs to be fixed > now specifically for touch events, cancelling review. It is something I ran in to while emulating touch events on the desktop. W3C DOM specs say it should be milliseconds[1]. Calculating the interval between events becomes hard when not all events us the same format. 1. http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-Event-timeStamp
Reporter | ||
Comment 6•12 years ago
|
||
This should be resolved with bug #77992. So closing this for now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•