-
Notifications
You must be signed in to change notification settings - Fork 46.7k
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
Adding visible state to Suspense Fallback component to enhance CSS transitions. #17296
Comments
You might be interested with the new |
Thanks @yanickrochon but the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
This is something we're interested in. Want to write an RFC? https:/reactjs/rfcs |
@gaearon on it, will try to take write up this weekend. |
Do you want to request a feature or report a bug?
Feature I suppose.
What is the current behavior?
Suspense fallback component flashes on and immediately unmounts (flashes off) when fetching is complete. See similar discussions here and here.
What is the expected behavior?
It would be ideal to add better transitions to the fallback component when it mounts and unmounts, but doing so requires using something like TransitionGroup or Framer Motion, which require a prop to listen to know when to mount and unmount. If we could somehow have the fallback component receive some kind of state from Suspense on when it is mounting and unmounting the fallback component, that would be great.
The text was updated successfully, but these errors were encountered: