Chrome Version: 59.0.3047.0
OS: Linux

What steps will reproduce the problem?
(1) Open https://rbyers.github.io/event-timing.html on Linux
(2) Drag with the mouse

What is the expected result?
My mouse is operating around 100hz.  I expected to see coalesced events whose timestamps are relatively evenly spaced (since I believe they should be getting majidvp@'s OS-timestamp logic).  

What happens instead?
The coalesced events all seem to have roughly the same timestamp:

frame[0]: events 0.5ms
frame[1] 14.2ms: events
frame[2] 17ms: events 0.2ms(0.4)
frame[3] 17.5ms: events 0.1ms(0.2, 0.1)
frame[4] 16.1ms: events 0.1ms(0.1, 0.1)
frame[5] 16.7ms: events 0.1ms(0.1, 0.1)
frame[6] 16.7ms: events 0.1ms(0.1, 0.1)
frame[7] 16.8ms: events 0.1ms(0.1, 0.1)
frame[8] 17.9ms: events 0.2ms(0.3, 0.3)
frame[9] 15.9ms: events 0.1ms(0.2, 0.2)
frame[10] 16.5ms: events 0.1ms(0.3, 0.2)
frame[11] 16.9ms: events 0.1ms(0.2, 0.2, 0.2)
frame[12] 16.5ms: events 0.1ms(0.2, 0.2)
frame[13] 16.6ms: events 0.1ms(0.2, 0.2)
frame[14] 16.4ms: events

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Chrome Version: 59.0.3047.0
OS: Linux

What steps will reproduce the problem?
(1) Open https://rbyers.github.io/event-timing.html on Linux
(2) Drag with the mouse

What is the expected result?
I assume my mouse is operating at 120hz.  So I expected to see coalesced events whose timestamps are relatively evenly spaced (since I believe they should be getting majidvp@'s OS-timestamp logic).

What happens instead?
The coalesced events all seem to have roughly the same timestamp:

frame[0]: events 0.5ms
frame[1] 14.2ms: events
frame[2] 17ms: events 0.2ms(0.4)
frame[3] 17.5ms: events 0.1ms(0.2, 0.1)
frame[4] 16.1ms: events 0.1ms(0.1, 0.1)
frame[5] 16.7ms: events 0.1ms(0.1, 0.1)
frame[6] 16.7ms: events 0.1ms(0.1, 0.1)
frame[7] 16.8ms: events 0.1ms(0.1, 0.1)
frame[8] 17.9ms: events 0.2ms(0.3, 0.3)
frame[9] 15.9ms: events 0.1ms(0.2, 0.2)
frame[10] 16.5ms: events 0.1ms(0.3, 0.2)
frame[11] 16.9ms: events 0.1ms(0.2, 0.2, 0.2)
frame[12] 16.5ms: events 0.1ms(0.2, 0.2)
frame[13] 16.6ms: events 0.1ms(0.2, 0.2)
frame[14] 16.4ms: events

In contrast here's what I see from Firefox on the same machine.  Presumably this represents the raw event stream, I'd expect to see a similar pattern from the getCoalescedEvents timestamps in Chrome.

frame[0]: events 2.5ms
frame[1] 16.9ms: events 14.7ms 6.9ms
frame[2] 16.1ms: events 15ms 6.9ms
frame[3] 18.9ms: events 18ms 10.1ms 1.9ms
frame[4] 16ms: events 9.9ms 1.9ms
frame[5] 16.5ms: events 10.4ms 2.6ms
frame[6] 15.6ms: events 10ms 2ms
frame[7] 16.7ms: events 10.8ms 2.8ms
frame[8] 17.1ms: events 11.9ms 4.1ms
frame[9] 24.8ms: events 1.6ms
frame[10] 8.6ms: events 5.3ms
frame[11] 15.9ms: events
frame[12] 17.2ms: events 6.4ms