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

It seems that from https://github.com/whatwg/dom/issues/23#issuecomment-185920481 the current requirement in DOM for `timeStamp` is not onerous and can be implemented across browsers.

It's not clear if we want to store two different times for each event, forever (different in both origin and resolution). (Though Apple seems okay with this given @rniwa's comment.)

It's also not clear what the compatibility impact is of changing `timeStamp`, exactly, though with Chrome shipping the change it cannot be huge, I think. Though as suggested earlier we might know more in a couple of months.

It seems unlikely other vendors will ship something fast, given https://github.com/whatwg/dom/issues/23#issuecomment-213079387 and https://github.com/whatwg/dom/issues/23#issuecomment-215242830, so maybe the best approach here is to just wait it out a bit and see what actually happens.

---
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-215418540