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

> This is the best possible breakage and they seem to be happy about the change.

What they said was:

> That also explains why this feature didn't work reliable on Firefox :)

In other words, they were already aware that their timestamp feature didn't work reliably on Firefox, but didn't know why. The reason they knew that the problem existed at all is because they have a highly generic library that works across events and reports timing, and **even they** weren't able to track down the details that led to the occasional inconsistency in Firefox.

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