Klaus Reinfeld Reporter
	Description • 9 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150903133607

Steps to reproduce:

The event.timeStamp value is too inaccurate and doesn't change between events.

Here an simple test case:

http://krpano.com/firefox/bugs/event_timestamp

1. open the browser console
2. drag the gray box
3. look at the delta_timeStamp values in the console - they should be bigger than 0




Actual results:

The time-delta between the events is almost always 0 because the timeStamp values are too inaccurate.


Expected results:

The timeStamp value should provide at least a millisecond accurate time.

	Karl Tomlinson (:karlt)
	Comment 1 • 9 years ago

Thanks for the nice testcase, Klaus.

For me, on win 7, 41.0b6, 41.0b7, and 40.0.3 all have similar behavior with timestamps increasing in multiples of 15 or 16 ms.

How often is the timestamp changing for you?

What do the timeStamp values look like.

I wonder whether you might be seeing bug 1048096.

Are you still getting expected behavior with Firefox 40?

Has the system been restarted in the last 25 days?

	Karl Tomlinson (:karlt)
	Comment 2 • 9 years ago

Noting that finding a regression window with Nightly will require setting dom.event.highrestimestamp.enabled to false.

	Klaus Reinfeld Reporter
	Comment 3 • 9 years ago

> I wonder whether you might be seeing bug 1048096.

Thanks! 
Yes, it's that bug.

It works now correctly after restarting the system.

	Karl Tomlinson (:karlt)
	Comment 4 • 9 years ago

OK, thanks.  Still a bug that should be fixed, but not a recent regression.