-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Navigation hangs after fast transition between states #2972
Comments
I think it has something to do with slow resolves (+/- 600ms) |
That seems strange... the ui-view named Can you provide a way for me to reproduce this? |
I'm facing the same issue. I'm not sure if it's the kind of example you're looking for, but I have a deployed example site that demonstrates this: https://tv-tracker-73580.firebaseapp.com/
Source code is available here: https://github.com/giannico/angular1-tv-tracker |
@giannico I fetched your code and ran it in a VM I think I may know why the reported behavior is happening, and I'd like to test against your app. |
Sorry @christopherthielen , it looks like the firebase version bump from 3.3.0 to 3.4.0 caused a breaking change in the application. I pushed the new package.json pinning the version to 3.3.0. If you just Thanks for taking a look. |
@christopherthielen, thank you, I confirmed the aforementioned issue is no longer present in the build you provided. The functionality is working great now. |
@christopherthielen Thanks, I'm hitting this as well. Any timeframe where this will make it into a new release? |
Navigation works as long as I don't navigate too fast between all the states. When I quickly navigate with some links with ui-sref on it, it freezes on a random state. You can see the difference between the working and non working navigation. The resolves are still called but the view aren't rendered anymore... We also use: $transition.router.stateService.target('state_name_palceholder') to navigate to other states and this still works but when navigating back to a corrupted state it gives back the freezed state.
a perfectly working navigation
The malfunctioning tracing looks like this:
The text was updated successfully, but these errors were encountered: