Users probably expect to see the top of encounters first when they click on an individual encounter page but often times, if they scrolled at all on the previous page, they find themselves in the middle of an encounter page.
This is made more apparent with leaderboards because you probably will be scrolling down the page quite a bit to see the encounter you are interested in.
We need to figure out a way to make sure users start at the top of the page so they can quickly get that high level information that's up there and not force additional scrolling on them.
One possibility is to tie UIkit's scroll function into the page load. I'm sure there are other options that might be better though.
Users probably expect to see the top of encounters first when they click on an individual encounter page but often times, if they scrolled at all on the previous page, they find themselves in the middle of an encounter page.
This is made more apparent with leaderboards because you probably will be scrolling down the page quite a bit to see the encounter you are interested in.
We need to figure out a way to make sure users start at the top of the page so they can quickly get that high level information that's up there and not force additional scrolling on them.
One possibility is to tie UIkit's scroll function into the page load. I'm sure there are other options that might be better though.