-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Allow specifying different transitions for navigation and popstate #14
Comments
Does this mean we can have transitions that go back and forth between pages in a single page app? I would be happy to see that. Maybe we could eventually get to do something like this? |
+1 |
Is there any updated? |
How about this feature now ? |
Until this get's an official solution, the method I've settled for is setting a "depth" meta property for each route. Then when the route changes, check whether the new route depth is higher or lower than the previous. If it's higher, transition from right, if it's lower (going back) transition from left. Not ideal and could be a nightmare to maintain, but get's the job done for simple implementations.
Or, if it's a super simple application, rather than set the depth manually, you can rely on the "depth" of the route path.
|
Transitions are extremely clumsy when using the swipe back gesture on iOS because they fire after the user has already reached the destination. Being able to disable transitions when a forward/back button or browser gesture is used would be very helpful. |
Have you found a work-around? I'm really struggling with transitions and swipe back gestures on iOS. |
I never found a workaround, just this issue |
Closing in favor of #3453 which would effectively allow this by using |
Sometimes different page transitions are needed when clicking a link vs. clicking the back button.
The text was updated successfully, but these errors were encountered: