Skip to content

RFC - Better State Transitions #700

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

Closed
thebigredgeek opened this issue Dec 18, 2013 · 4 comments
Closed

RFC - Better State Transitions #700

thebigredgeek opened this issue Dec 18, 2013 · 4 comments

Comments

@thebigredgeek
Copy link

I am sure everyone else has noticed that when you change the state, it jumps to the top of the screen as though it is reloaded. There has to be a worthwhile solution for this, and this is definitely a must-have for my organization so I am willing to dedicate time to solving this. Changing a child state SHOULD ONLY CHANGE THAT VIEW, not render everything else. Is anyone else willing to help me with this?

@timkindberg
Copy link
Contributor

I'm happy to help out. I think its just a problem with the $anchorScroll though, because ui-router already functions in the way you describe—changing only the views that need to change. I thought that the problem is it scrolls to the top too.

@thebigredgeek
Copy link
Author

Also, I'd really like to make it possible to do non-linear routing with angular. Currently, you can only have one route/state active at a given time. This isn't great for apps that are very sandbox in design, with multiple states all containing child states simultaneously

@timkindberg
Copy link
Contributor

One thing at a time :) that's a hefty one to tack on.

@nateabele
Copy link
Contributor

This issue is conflating two separate issues, both of which are covered elsewhere, so I'm closing this as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants