Question

"Open overlay" resets main component scroll position BUG

Forum|Forum|3 years ago
September 20, 2023
20 replies
1843 views

Issue: Open overlay resets parent frame scroll position, even tho it is not checked. (Only new state prototype ones are scrolling up)

That’s it, as simple as that. I don’t know why.

Ask the community

This topic has been closed for replies.

Show previous replies

Horlle_Design1

New Participant

Having the same problem here for some time.
Using the new state management system, clicking and opening an overlay always resets the parent frame scroll position to the top, no matter if that option is on or off.

s1110

Same issue. Any updates?

Frederic_Fornini

Active Member

This is still an ongoing issue, which is a downer for prototyping.
There is a workaround though, it is not ideal but in the meantime it does the job.

You don’t check the box “reset scroll position” and you had to the target overlay :

After delay / scroll to 'insert top bloc name here" / Instant.

You can also do this when you close the overlay, which is a tad better animation wise.

Mariam

Having this issue, any updates?

Quentin1

Same issue here, any news?

djv

Community Support

Hey All, our team hasn’t been able to consistently reproduce to find a solution yet.

As mentioned above, we did narrow down that the issue seems to only occur with main components and not instances of those main components. Is anyone able to share specific cases or scenarios that you need to use a main component over an instance?

uiuXtina

Sorry if I’m stating the obvious, but the tool tip right next to “State management” solved the issue for me, regrettably after much time spent trying to figure it out:
“Preserve scroll position is automatically applied when top-level frames have identical names or matching prefixes.”
So, after updating my frames to have matching prefixes, it worked flawlessly.

Here’s a super simplified example. (attached video) You can see the frames are prefixed with “drawer/”

(The key with prefixes is that you must use a forward slash- no dashes or anything else will work. It would also work if the frames have the exact same name, but that becomes too difficult with multiple frames.)

Hope this helps!

e0ae4f45bbd992eb864d258df5ffd88b26ab08c0.zip

Aaron15

New Member

Our team ran into this issue. The page in our prototype flow was turned into a main component because we have instances of it in a presentation space that needs to stay in sync with the latest designs.
Knowing this now, it’s an easy enough work around to create a separate instance of everything specifically for prototyping, but that feels unnecessarily repetitive and wasn’t the expected behavior.

Emil_Holm

Can you please fix this? It’s an ANCIENT bug and it makes it impossible to prototype properly if you have multiple consecutive overlays.

This error happens when:

From a regular frame/page I open a Overlay. After a delay I then swap the overlay. After another delay I navigate to a different frame/page. Even though I’ve selected not to reset scroll position, it resets the scroll position.

Hope this helps fixing it. It would add like 18 more pages if I need to create new pages instead of overlays…

Claudio_Fresta_Suharno

New Participant

i also got this. wow, this hasn’t been fixed? do I have to convert my overlays to screen?

current situation:

screen A: overflow-y scroll, initial position: 30px from the top, one field is empty

screen B: modal bottom sheet for overlay on top of Screen A when the field on Screen A is clicked

screen C: a duplicate of screen A with the field that used to be empty, now it is filled, figma prototype made the scroll position reset to 0px (top)

expectation:

when screen B clicked, the expectation should be:

go to screen C, where the position is 30px from the top

Sign up

Login with SSO

Login to the community

Login with SSO