Bug Tracker

Opened 11 years ago

Closed 11 years ago

#11464 closed bug (invalid)

event.timeStamp is a Date object rather than an integer in Android

Reported by: [email protected] Owned by: [email protected]
Priority: low Milestone: None
Component: event Version:
Keywords: Cc:
Blocked by: Blocking:


Tested on the default Android 2.3 browser, and on the Android 2.3 Dolfin browser. Event timestamps are not being normalised to millisecond values, but in some Android browsers they are reported as Date objects.

Proposed fix in this commit: https://github.com/stephband/jquery/commit/03f7c08a8483bfc44893a38eafb329e47428fe74

Change History (4)

comment:1 Changed 11 years ago by Rick Waldron

Component: unfiledevent
Priority: undecidedlow

Before we bother messing with it, this should be reported to webkit. If they say "no" then we can discuss doing something

comment:2 Changed 11 years ago by Rick Waldron

Version: 1.7.1

comment:3 Changed 11 years ago by dmethvin

Owner: set to [email protected]
Status: newpending

We've been trying to wave people off using event.timeStamp since it's also broken in Firefox (since *2004*!). What is your use case that isn't resolved by using new Date() to get the current time in the event handler?

comment:4 Changed 11 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.