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

At the moment I tend to agree with @domenic. Based on current data and our beta experience until now the impact appears to be limited in scope (although subtle) and within our expected range. Not sure if we should change our strategy yet.

To be fair, most of the code that tries to compare Event.timeStamp with Date.now() is already broken in subtle and not so subtle ways:
 - Not dealing with system wall time skews 
 - Improperly handling firefox [edge cases](https://bugzilla.mozilla.org/show_bug.cgi?id=238041)  (e.g., In Firefox value may be: zero, a unix epoch but in microseconds, or millisecond value in system startup time).
 - Invalid comparison between monotonic and non-monotonic clocks In Safari which can lead to subtle bugs. (In safari, the event timestamp is [monotonic but with unix epoch timebase](https://github.com/whatwg/dom/issues/23#issuecomment-142292155) )

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/23#issuecomment-181579384