Re: [whatwg/dom] High resolution timing for events (#23)

Just some data, `event.timeStamp` has been a PITA to jQuery for a long time since people expected us to fix it. It was broken in Firefox until 2014 and broken in Opera until 2012. We also [received a report](https://bugs.jquery.com/ticket/11464) in 2012 that it was broken on Android 2.3 Dolphin. So anyone depending on reliable cross-browser results has been getting wrong answers until the last 3 or 4 years.

jQuery used to try patching this problem by filling in a `Date.now()` value for the timestamp if it was zero but [removed that code](https://bugs.jquery.com/ticket/10755) in jQuery 1.7 (January 2011). I hope that encouraged people to stop using the value altogether, but you can still find various GitHub code and StackOverflow answers that assume the timestamp is compatible with `Date.now()`.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/23#issuecomment-215597473