Re: [whatwg/dom] Update Event.timeStamp type to DOMHighResTimeStamp. (#420)

> Do we have tests already?

No I have not upstreamed the test yet. I was thinking to have this PR first and gain some confidence that it is accurate and then refer to it when upstreaming the test.

Also, hr-time spec has [recommendation](https://w3c.github.io/hr-time/#privacy-security) on limiting the minimum resolution of the clock exposed via performance.now() to prevent certain types of timing attacks. Given that synthetic events will use the same clock, they can be used to the same effect (e.g., repeatedly creating events and reading their timestamp). We have made sure to prevent this in Chrome. I think we should add some language to the spec (perhaps a note?) recommending the same thing. wdyt?

> the recommended minimum resolution of the Performance interface should be set to 5 microseconds.


-- 
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/pull/420#issuecomment-285504782