Closed Bug 785076 Opened 13 years ago Closed 13 years ago

[AccessFu] Work around timestamp issue in emulated touch events.

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla17

People

(Reporter: eeejay, Assigned: eeejay)

Details

Attachments

(1 file)

No description provided.
Comment on attachment 654615 [details] [diff] [review] Work around touch emulation timestamp issue. Review of attachment 654615 [details] [diff] [review]: ----------------------------------------------------------------- r=me with considerations below: ::: accessible/src/jsat/TouchAdapter.jsm @@ +87,5 @@ > let touches = aEvent.changedTouches; > + // XXX: Until bug 77992 is resolved, on desktop we get microseconds > + // instead of milliseconds. > + let timeStamp = (Utils.OS == 'Android') ? aEvent.timeStamp : > + new Date().getTime(); Date.now() is much faster than (new Date()).getTime(); Also, you could call timeStamp "time" or "now" if you wanted.
Attachment #654615 - Flags: review?(dbolter) → review+
Assignee: nobody → eitan
(In reply to Eitan Isaacson [:eeejay] from comment #3) > https://hg.mozilla.org/integration/mozilla-inbound/rev/d636babbf532 > > Thanks for the Date.now() tip.. I really shouldn't give dating tips.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: