-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
useTransition: How to start / stop; and performance issue #903
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.
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
Comments
There is a pausing mechanism in the latest canary (see the Eventually, it will be, and if you have time to implement it, you can open a PR that adds Hope that helps. ✌️ |
Thanks for the information! That helps a lot. I will try to look into this and maybe make a PR in recent days. Which branch should I work on? |
The I'm not aware of any performance problems, so I suspect it's specific to the browser and OS. If you can create a demo that reproduces the issue, I'll take a closer look if I get time. LMK if you have any problem setting up the repo locally. |
Closed by #911 |
I'm building bar chart race animation with useTransition. here is the source and demo. I have the following questions:
I'd like to build a play / stop button for it. But I couldn't find a way to play / stop the transition in the document. Is there any way to do it?
The animation is janky on firefox android(at least on my device) but smooth on chrome android. I found out (with react profiler) that render
<RacingBarGroup>
(which calluseTransition
for animating the bars) cost lots of time. Is there any idea for optimizing performance?I noticed that the other bar chart race implementation using vanilla js and d3 is smooth on firefox android (for example https://observablehq.com/@d3/bar-chart-race), so I'm not sure this issue is due to my code, react-spring or react.
I previously posted this on spectrum, but I got no answer there so I created a new issue here. Sorry for bombing if you've read my questions on spectrum :-/
The text was updated successfully, but these errors were encountered: