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

I want to reiterate a few things (excuse me for being brief as I am on mobile):

> shows the impact is likely to be < 0.02%

That appears to be higher than @RByers's proposed threshold of 0.01% (which is 1 in 10,000 sites):

> If we find a pattern that, say, we find used on >0.01% of the top sites in httparchive then we should definitely reconsider.

Also, the analysis:

> * e.timeStamp - value
> * value - e.timeStamp

That does not cover any of the reported cases, including [Angular's](https://github.com/angular/angular.js/pull/13495/files) use case.

> ...and I have assumed breakage if the usage was not obvious.

None of the reported cases hard errors and only break in ways that cannot be easily detected.

> ...the fix has been trivial...

Unfortunately, fixing a library going forward doesn't affect existing deployments. It by definition is irrelevant to web compat.

So, I don't agree that we have data to prove that this doesn't matter, even if it has shipped in Chrome beta.

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