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

Hello,
I have to many lines in my Prototype (over 200?). How can I check “Preserve scroll position” in one click in every line in my prototype? Its annoying to click every one ☹

Thanks,
Ania

My gut says to select all the lines, put them in a group or frame, and then click “Preserve scroll position” on that group or frame.

But there is impossible to select all. You can select only one… 😦

After the recent state management update, I have noticed an issue. Whenever I perform ‘navigate to’ interaction to another page, the scrolling position is always reset, even though the “reset scrolling position” option is unchecked. However, in the older version where it was still “preserve scroll position,” the interaction worked perfectly fine. Has anyone else experienced the same issue?

I have the same issue.

I have exactly the same issue… which kind of “ruined” my prototype. Anyone can help?

i found the problem, the top level frame name should be identical with the target frame, otherwhise the preserve scroll won’t work

This solved it! 🙏

“the top level frame name should be identical with the target frame, otherwhise the preserve scroll won’t work.” This works to me

You need to create variant to preserve scrolling position

I also faces the same issue since yesterday. @Figma_Support please roll back the feature.

Hi all, if you are experiencing an issue we would like to take a closer look. Would you mind reaching out to our support team so they can assist further Submit a bug form →

same here… its super annoying

Identical as in “with the same name” though.

Is that really the intended behavior? Feels like a bug because, at least in my workflow, it’s completely normal to have each frame named differently (“before click”, “after click”) and still want to have the scroll position preserved.

u can still have different frame names on your flow, but now you need to add dash ‘/’

for example ‘main menu / before click’ and ‘main menu / after click’.

Those are considered identical because figma only read the frame name before dash ‘/’

that rule is also written on the documentation

Woot, that works!

Seriously had no idea about this. (But I’m a fresh XD refugee, so maybe that’s why…)
Thanks!

Same thing. Prototypes break and start twitcing on interactions.

I’m having the same issue here! The suggestion to make sure the top-level frames are named the same did seem to fix it, but it’s not an ideal solution when my frames are named separately for a reason… Hopefully we can get a fix for this!

I’m facing the same problems here guys! It seems to be more like a bug from this new update, to me you know. Like our friend @phroobin said, when we change the names of the frames to the same name, it works pretty well. But i’ve got 35 frames here dude, so we do need to give different names to identify those guys later. We all need to report this bug to the Figma Support, I guess. The more we all report, the sooner they will hear us and take a closer look at this issue. So let’s do it! 👍t4:

Why is there silence from @Figma_Support about it? This is a big issue. I have to use another tool.

I have the same issue and it is a big problem. When can this get fixed or rolled back?

I created frame in middle of page frame, and added hover state.
Now when test in prototype it simple throws me on top on new frame…

Earlier was there ‘preserve scroll location’ now it’s missing. There is something new ‘Reset scroll position’ which is turned off. That means preserve is default. But it’s not working …

Hey @Figma_Support! Can you guys help us by fixing this bug please? 🙏🏾

Answer from @Helge_Wadewitz works for me. All frames where you want scroll position to be preserved must be named the same. Seems like much the same way that layers must be named identical for smart animate to work.

Regardless, its frustrating not being able to name frames with different names. @Figma_Support please fix this.