Closed muffinresearch closed 8 years ago
Oh thanks for reporting this, it’s an issue across the site that’s been irking me. I think we’ll want to move the page position to .App-content (below the search bar) after any route change.
There are router middlewares to deal with this in relation to history: https://github.com/taion/react-router-scroll which is probably what we want.
I'll try out the middleware and report back. Looks to work correctly so I'm making a PR.
Verified as fixed using https://amo.addons-dev.allizom.org/en-GB/firefox/ in responsive mode under FF51(Win 7) and AMO-dev on my Android 6.0.1 device. Postfix video:
Describe the problem and steps to reproduce it:
What happened?
The details page is loaded at the same scroll position as the click:
e.g:
What did you expect to happen?
The scroll position should be the top of a new page after navigating. However, clicking back should keep the original scroll position.