Reset scroll position of an overlay when closing

Ask the community
1

Hi all,

I’ve been running into a scroll position issue since state management was introduced.

I have a page with various buttons, and when selected, opens an overlay. These overlays have scrollable content on them, allowing the user to view the content. If the content has been scrolled and the overlay closed, when reopening the overlay the scroll position hasn’t been reset.

I have the option to ‘reset scroll position’ on the button-to-overlay interaction, but this resets the main page and there is no 'reset scroll position on the ‘close overlay’ menu interaction.

I ran a test there the overlay was treated as a new page (so ‘navigate to’ instead of ‘open overlay’) and the ‘back’ interaction on the overlay has the option to reset and behaves as expected.

What am I doing wrong? I know the state management setup indicates that layers need to be named the same, but this is to maintain scroll position. I need to reset the scroll position on the overlay once it has been closed.

Thanks

2 Likes
2

Hi all, I have the same problem in my overlay and would like to learn a solution for this.
Many thanks

3

I have the same issue

4

Same issue here. When “open overlay” is selected as an interaction, the overlay does not reset scroll position even if I have selected “reset component state”. This has worked previously and doesn’t.

Does anyone know solution to this issue?

5

Same problem here. Would be easy to have an “Reset scroll position” option as for other interactions and keep the default to not reset it.

6

Same issue here. This is wreaking havoc on our prototypes for usability testing and really starting to test our patience. I honestly can’t think of a reason why i’d want to reset the scroll position of the page when opening an overlay so this reeeeallly feels like a bug.

7

I have the exact same issue and would love to know if there is a solution or workaround!

8

Same problem here… just a checkbox for reset would be enough i guess

9

Same issue here. A year later, there is still no solution?