fix(scheduler): getNow detection can randomly fail (#9667)

The previous detection code compared time stamps based on Date.now()
which are not monotonic, so the check could fail due to clock skew or
adjustments.

This fix changes the check to compare against performance.now() if it is
supported, because it is monotonic (strictly increasing).
This commit is contained in:
Felix Bünemann 2019-03-11 03:28:06 +01:00 committed by Evan You
parent 781c70514e
commit ef2a380c6e

View File

@ -51,7 +51,7 @@ if (
inBrowser &&
window.performance &&
typeof performance.now === 'function' &&
getNow() > document.createEvent('Event').timeStamp
document.createEvent('Event').timeStamp <= performance.now()
) {
// if the event timestamp is bigger than the hi-res timestamp
// (which is evaluated AFTER) it means the event is using a lo-res timestamp,