Fix timestamp not updating occasionally#3066
Merged
compulim merged 3 commits intomicrosoft:masterfrom Apr 3, 2020
Merged
Conversation
corinagum
approved these changes
Apr 2, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Entry
Description
Chrome may sometimes fire
setTimeoutbefore the scheduled time.In that case, when we calculating the next scheduled time, it will be the same value of the current schedule. In our
useTimeouthook, if the scheduled time kept the same, it will not reschedule it.Thus, some timestamps may stop updating.
We are adding a bit randomness to make sure the next scheduled time is slightly different and will continue to fire.
Specific Changes
useForceRenderAtIntervalto add randomness on schedulingTesting Added