Re: [pointerevents] Should pointer events and compatibility mouse events have the same timestamp? (#284)

I agree the spec doesn't require this, so relaxing the tests seems fine.

That said, a couple years ago I believe we did [get agreement]( that `Event.timeStamp` was the right way to [measure input latency]( So it would seem confusing to me for a `pointerdown` to have a different start time from it's equivalent `mousedown` - it would suggest that one or the other doesn't really reflect the real input latency. Isn't there a risk that this could break sites own [measurements of their input latency]( It looks like the [FID polyfill]( just pays attention to the first event it sees and listens for both `pointerdown` and `mousedown` so as long as WebKit uses the real original timeStamp for `pointerdown` it should be OK. But others may not be.

GitHub Notification of comment by RByers
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 28 May 2019 14:34:07 UTC