Skip to main content

Bug Tracker

Side navigation

#11464 closed bug (invalid)

Opened March 12, 2012 12:34AM UTC

Closed April 18, 2012 08:12AM UTC

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

Reported by: Owned by:
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:

Attachments (0)
Change History (4)

Changed March 12, 2012 04:14PM UTC by rwaldron comment:1

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

Changed March 12, 2012 04:14PM UTC by rwaldron comment:2

version: 1.7.1

Changed April 04, 2012 02:18AM UTC by dmethvin comment:3

owner: →
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?

Changed April 18, 2012 08:12AM UTC by trac-o-bot comment:4

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!