Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(scheduler): getNow detection can randomly fail (fix #9632) #9647

Merged
merged 2 commits into from Mar 8, 2019
Merged

fix(scheduler): getNow detection can randomly fail (fix #9632) #9647

merged 2 commits into from Mar 8, 2019

Commits on Mar 7, 2019

  1. fix(scheduler): getNow detection can randomly fail 

    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).
    @felixbuenemann
    felixbuenemann committed Mar 7, 2019
    Copy the full SHA
    c8041dc View commit details
    Browse the repository at this point in the history

Commits on Mar 8, 2019

  1. Update scheduler.js

    @yyx990803
    yyx990803 committed Mar 8, 2019
    Copy the full SHA
    341f6a6 View commit details
    Browse the repository at this point in the history