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

> It seems transitioning to high-precision timer since posix epoch may address the concerns being raised, with what seems like little cost? Maybe I'm missing something...

In that case the timeStamp value will look similar to Date.now() but only on surface. The actual value is coming from a different monotonic clock which unlike Date.now() is not impacted by NTP time skew. This means that the developers are more likely to compare it with Date.now() which is going to break in subtle  ways in random machine which makes the bug hard to detect. To quote dbaron from [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1231619#c11)

> Shipping a feature where a developer getting it wrong means their page is intermittently broken on a small percentage of machines seems pretty bad.  Seems like people are likely to get that wrong forever.  It seems better to actually go through a more-breaking change once. 

If we decide not to change Event.timeStamp then a better solution is to actually use a different attribute.

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