Use the timeStamp member of events when performing time calculations

NEW
Unassigned

Status

()

Core
DOM: Events
4 years ago
8 months ago

People

(Reporter: birtles, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

4 years ago
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 1

4 years ago
Created attachment 8441745 [details] [diff] [review]
WIP part 1 - Convert AsyncPanZoomController

Originally part 5 from bug 77992.
(Reporter)

Comment 2

4 years ago
Created attachment 8441746 [details] [diff] [review]
WIP part 2 - Convert nsListControlFrame

Originally part 6 from bug 77992
(Reporter)

Comment 3

4 years ago
Created attachment 8441747 [details] [diff] [review]
WIP part 3 - Convert nsIDOMEvent::GetTimeStamp

Originally part 7 from bug 77992.
(Reporter)

Updated

4 years ago
Blocks: 1026809
(Reporter)

Updated

2 years ago
Depends on: 1256562
(Reporter)

Updated

2 years ago
Depends on: 1256565
(Reporter)

Comment 4

a year ago
I think Ben was interested in looking at this.
Sure. Take this bug to check.
Assignee: nobody → btian

Comment 6

8 months ago
De-assign myself for not actively working on this bug.
Assignee: btian → nobody
You need to log in before you can comment on or make changes to this bug.