SOLVED - Preserve Scroll Position (please roll back the feature)

Seems that solution is that frames must have same name, and then by default scroll position will be reserved.

Yup that works for me too, but I agree that it’s not very intuitive though.

The same naming niether works for me.

Thanks for suggesting this fix, that seems to be helping for now. But I would expect the preserve scroll option to be brought back as an option, this took a few hours to figure out!

I have my frames/objects named the same between top-level frames, and they show up as the same object when I select an object in one of the top-level frames (indicated by purple outline on object in each top-level frame), but the scroll position isn’t being preserved properly when navigating back and forth - jumps several pixels in each direction. This worked much better in previous state management. Hope they fix this soon.

It is totally untenable/unworkable to have to name top-level frames identically to get prototyping working correctly. I shouldn’t have to conform my system for naming top-level frames to get prototyping to work correctly. This was NOT an issue or requirement in previous state management. And even when I do name them the same, the scroll position still jumps several pixels between frames.

Got to admit that the “name / subname” fixes things. So in a particular flow I just adjust name to “1 / current frame name” to keep things simple and not having to throw away my naming system.

Having the same issues as everyone else mentioned in this thread and prototype looks flawed. I need this to present to important clients but not in its current state. It looks unprofessional and clunky in and @Figma_Support needs to help sort this for everyone as soon as they are able?

Hi all,
Thanks for reaching out about this and our apologies for the disruption!

It sounds like you’ve run into some issues related to the limitations with the new State management for prototypes update, and for most users this is because the layers do not share matching names. In order for top level frames to share scroll state, they need to have matching names according to this rule.
=> Tips: for the frame naming, you can have different names but need to be identical before the ‘/’. (cf. screenshot)

If you are still running into issues after trying this, please reach out our technical team here.
Please also make sure to use your Figma account email, including a link to the file, and share it with support-share@figma.com as an editor on this file so the team can take a closer look.

Thank you!

I added them to my file, in there you can see on the “C/Services Active” flow the frames are named the same but will still have the scrolling position reset in the prototype 😦