Open
Bug 1026806
Opened 10 years ago
Updated 2 years ago
Use the timeStamp member of events when performing time calculations
Categories
(Core :: DOM: Events, defect, P3)
Core
DOM: Events
Tracking
()
NEW
People
(Reporter: birtles, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
25.22 KB,
patch
|
Details | Diff | Splinter Review | |
5.16 KB,
patch
|
Details | Diff | Splinter Review | |
691 bytes,
patch
|
Details | Diff | Splinter Review |
Bug 77992 and follow-on bugs mean we now store event times both as 64-bit integer and as a TimeStamp. The integer field is very inconsistently set, sometimes representing milliseconds, sometimes microseconds, and using different zero times, often platform-specific. Long-term we should standardize on storing as TimeStamp and remove the integer field. Before we remove the integer field however we need to convert all calculations that depend on the integer field to use the TimeStamp field instead.
Reporter | ||
Comment 4•7 years ago
|
||
I think Ben was interested in looking at this.
Comment 6•7 years ago
|
||
De-assign myself for not actively working on this bug.
Assignee: btian → nobody
Updated•6 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•