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

Totally agree!

C’mon @Figma please make this easy adjustment and save everyone!

the prototype still jumps all over the place

@SP13 — Sorry this is happening. In cases it is happening for scrolling containers inside of top level frames: they need to match to each other across frames. Read more about matching of nested objects…

If it’s not scrolling set on nested objects, could you send a screenshot or sth and I can see if I can reproduce it.

Wondering why there cannot be three checkboxes on the interaction modal with these choices

We’ve actually thought about this , too, but there are two reasons why we didn’t end up with this:

1. We wanted to have the ability to “remember” a screen at the position that you were scrolled to. (Imagine a long list of products that you scroll down. You click on one and you go back; Normally you’d be back at the top, but real apps remember your scrolling state.) —> That’s not possible just with “Preserve scroll position”.

2. We wanted the system of State management to be consistent across all “interactive elements”, so it works the same for Scrolling, Videos, and Interactive components. And given that “Preserve video position” or “Preserve interactive components” wouldn’t have worked for the same reasons as in 1., was another reason to go for the new behavior.

I hope that helps a bit in understanding why we did this change, but yeah, we’re very sorry it caused this much confusion during rollout on this and we learned a lot of what not to do when changing behavior in Figma.

If you have cases where it just doesn’t work, LMK and we can take a look if anything is buggy.

Context: I was the designer on this feature.

@nikolasklein Thank you for responding - I wonder if you could put out a tutorial video about the new feature, showing step by step how to use it. This would be a huge help.

@SP13 — I’ll ask! We have a new Help Center article about State management that goes quite into detail about how it should work.

Let me know if that’s insufficient!

My prototypes are also unusable. I’ve spent a half an hour trying to make a simple interaction work. Digging through dozens of frames to try and diff the layer names to make sure they are identical… extremely frustrating. Especially when it appears all of these dozens of layer names do in fact match — but it still won’t work. I’m beating my head against a wall over here for what used to be an easy thing to manage with a checkbox click.

I would also appreciate a rollback to the previous implementation of state management, where scroll position was managed with a checkbox.

Have the same issue, since Figma Config features rolled out.

Thank you so much mate! 🙏🙏🙏 Worked like a charm!
Even the animations weren’t performing correctly before. Now they’re behaving exactly how I wanted them to be.

You saved me from embarrassing myself in front of everyone. Haha Thanks!

Please roll back this feature. The naming convention thing is not a sustainable “hack” for us to use. I am trying to open an overlay in a manual position on the page but it keeps resetting the scroll position. The name of the page(frame) is “Home” and the overlay frame name is “Dropdown” but its still resetting the scroll position. Please roll back! So frustrating.

This…does…not…work, and is not solved. PLEASE roll it back! It preserves scroll in one direction, and then not the other. It’s buggy, unpredictable, and so unbelievably frustrating! I keep hearing Figma team responding with “We wanted…we wanted”, but it’s not about what you want, it’s about what works and is useable, and this is neither of the two.

Please at least give us the option to use a checkbox as well. If it was solved, people wouldn’t still be complaining.

I agree, it’s not solved.

Today I added another pop-up component to my prototype.
Now opening this with those settings:

Scroll state property is the one you currently parse out of the name. “root”

Btw, its bug for sure, since if I create totally new project with the same settings, I get different results.