You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't quite as easy as one could have hoped, as controllers etc. loads data into views causing re-rendering, the scrolling as is may actually scroll to a wrong location.
And waiting for the views to load fully is actually suddenly a difficult task inside Angular's design, unless we provide some sort of "signalling" for the developers to use inside controllers which i just feel is a bad idea all together.
So maybe turning this on it's head and providing the service combined with a directive that can then scroll ones it's element is loaded may provide a better option, although I could still see some cases where it would maybe scroll and then render new content above again causing the scroll location to be wrong.
This could also be another service that simply used AnchorScroll as default behavior (depending on it) and then extends it.
Things that should be possible is to scroll to elements defined by a route parameter etc.
The text was updated successfully, but these errors were encountered: