I have 2 pages in an app with multiple sections on the page. Both pages have data rendering from APIs.
If the user uses the back or forward button in the browser, the page scrolls automatically to a position on the source page to match the position of the destination page before loading the destination page. This creates an un-intended experience for the app.
Example scenario -
- I am on page 1, top section (section 1). I scroll down to section 3.
- I navigate to page 2 from page 1.
- Page 2 loads to of the page.
- I scroll down to section 5 on the page.
- When I hit the back button on the browser, page 2 scrolls up to match section 3 position from page 1; and then page 1 is loaded.
This only seems to be happening on the published site, since the pages are reloaded inside the editor when navigating back and forth using browser back and forward buttons.
