Stop using requestAnimationFrame #85
Merged
Conversation
This file contains 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
|
Thanks a lot! I was just learning about tasks vs micro-tasks the other day, so this makes perfect sense :) |
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.
When opening a popup I'm seeing the popup first show up at (0, 0) before moving to its correct position. (Demo: click the top-left logo of https://decomp.me/scratch/5MmAZ.) This appears to be because useLayer delays position updates by one frame using requestAnimationFrame -- removing that delay fixes the problem for me. I'm not sure if there's a concrete problem that the requestAnimationFrame is there to fix; I tried to maintain some of the original throttling by using an immediately resolved promise.
Possibly related to #61, #68, #79.