Fix negative timeSincePreviousFrame
in useFrameCallback
#8135
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.
Summary
When we handling events, all queued callbacks are flushed (here) with the event's timestamp instead of the frame target timestamp. As a result, frame callbacks can execute more than once per frame, leading to negative values for
timeSincePreviousFrame
. This change adds a new parameter to the__flushAnimationFrame
method to distinguish the origin of the flush and skip unwanted frame executions.This issue doesn't affect regular animations since they don't rely on the time delta since the last frame but rather from the beginning of the animation.
before.mov
after.mov
Test plan
code