Ticket #11464 (closed bug: invalid)
event.timeStamp is a Date object rather than an integer in Android
| Reported by: | stephband@… | Owned by: | stephband@… |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | event | Version: | |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
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
comment:1 Changed 15 months ago by rwaldron
- Priority changed from undecided to low
- Component changed from unfiled to event
comment:3 Changed 14 months ago by dmethvin
- Owner set to stephband@…
- Status changed from new to pending
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 13 months ago by trac-o-bot
- Status changed from pending to closed
- Resolution set to invalid
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!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
Before we bother messing with it, this should be reported to webkit. If they say "no" then we can discuss doing something