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

Same ! It’s a terrible update. How to ruin your work when you have to present a prototype 😦 😡

Fix this issue! Supper annoyed!

This update is not making our prototypes behave in a predictable way when walking stakeholders and clients through them in a demo situation. It’s very jarring when the page unnaturally jumps to the top.

The suggested ‘fix’ to name the top-level frames the same works but as others have pointed out, is not ideal when you want to give different names to identify each screen for organisational purposes. Unique frame names help during construction of the prototype. We have ~20-60 frames and with the same name we’ll have to guess which is which in the interaction details menu.

Agreed, the best solution is to just keep the ‘Preserve scroll position’ checkbox and make it checked by default regardless of same frame names…

I’ve had to complete re-work my prototypes and they’re still not 100%

I am having the same issue on all my prototypes. I have tried to go fix and update the interactive components and the wired interactions, but on anything that was built prior to the update the scrolling is bugged. I even tried re-wiring the entire prototype from scratch again, but still didn’t fix it. Please Figma, PLEASE roll back this feature or figure out a fix. I don’t want to have to rebuild all my designs from scratch…

Gosh))) it’s been like 20 days, that’s something super easy to fix. Guys, if you think we will used to it, unfortunately no… How long to wait when my proto’s going to be fixed?

I was having the same issue but the note from support above really helped for my NEW protoypes.

Essentially the only part of the artboard name that has to be the same is the beginning if the artboard, then add “/” and everything after can be unique. SDo you dont have to have 30 frames with the name “default load”

I just renamed all my desktop frames
DT/default load
DT/input open
DT/tooltip

You get the idea. Anyway, it fixed everything and it works perfect now.

The thing I’m dreading is going back over older prototypes.

@Figma_Support we need an update. Are you rolling back? How long will it take?

We need a “Preserve Scroll Position Across Pages” that is separate from the new State Management settings. I don’t want Page A to remember its scroll setting and Page B to remember it’s own different scroll setting, I want Page B to MATCH Page A’s scroll position when I navigate to it.

Expecting users to use a naming convention when it wasn’t required before is not a good practice, and even if the naming convention is followed it doesn’t work as outlined above.

Totally agree with you