ComputeDeadline always returns a value less than 16ms (on 60Hz refresh-rate devices)

[rniwa]

Despite of the fact computeDeadline algorithm uses 50ms upper limit and only shortens it to the estimated next rendering update when there is a rendering update opportunity, both Firefox & Chrome seem to always behave as though there isa rendering update opportunity, and always returns a time less than 16ms on a foreground tab / window.

[smaug----]

http://mozilla.pettay.fi/moztests/maxidletime.html gives me ~50ms deadlines most of the time, both in Firefox and Chrome, on Linux and Windows. (Didn't have a Mac around)

[annevk]

@rniwa could you perhaps share your test so we can contrast it with the one from Olli?

[rniwa]

I have no recollection of this issue. Closing for now.