1026806 - Use the timeStamp member of events when performing time calculations

Status: NEW

(Core :: DOM: Events, defect, P3)

Description

[Brian Birtles (:birtles)]

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.

Comment 1

[Brian Birtles (:birtles)]

Attachment: WIP part 1 - Convert AsyncPanZoomController

Originally part 5 from bug 77992.

Comment 2

[Brian Birtles (:birtles)]

Attachment: WIP part 2 - Convert nsListControlFrame

Originally part 6 from bug 77992

Comment 3

[Brian Birtles (:birtles)]

Attachment: WIP part 3 - Convert nsIDOMEvent::GetTimeStamp

Originally part 7 from bug 77992.

Comment 4

[Brian Birtles (:birtles)]

I think Ben was interested in looking at this.

Comment 5

[Ben Tian (inactive)]

Sure. Take this bug to check.

Comment 6

[Ben Tian (inactive)]

De-assign myself for not actively working on this bug.