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

This is just horrible. Figma is becoming a very convoluted tool. I don’t event know why I’m bothering with prototyping here. I’ll just use marvel.

Hi, we made the changes to preserve scroll position, to make it more consistent & we’re sorry for the disruption! To be clear, since May 24, scroll position of top-level frames is preserved automatically when they have identical names OR a shared prefix followed by a forward slash (e.g. “Checkout/1”, “Checkout/2").

Any new interaction automatically follows new state management rules. To update an old interaction to the new state management controls, click the Update button on the Interaction details modal.

This help center article will help you quickly update your frame names for an existing prototype: https://help.figma.com/hc/en-us/articles/360051747774#Changes_to_preserve_scroll_position

If you still have questions, feel free to reach out our support team here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001731233

Give us the ability to preserve scrolling position without having to rename the frame. The fact that you closed this topic just to not have to deal with angry people says a lot about you and how you handle feedback from the community. Your ‘frame naming solution’ is ridiculous. No one is gonna rename their infinite number of frames. The fact that you refuse to fix this boils my blood and I hope you resolve this issue instead of sweeping it under the rug like you did with the previous bug report with this title.

Hi there! Thanks for your feedback. We hear you, we will pass your feedback to the team for consideration.

I switched your topic as “Share an idea” so we can gauge the overall interest in the community.

it’s not “an idea” it’s a bug and you need to fix it! so so many people wrote on the original post that they’re incredibly frustrated and all you do is avoid the topic! Instead of rolling back the feature you keep ignoring it as if everyone’s fine with it. we are not fine with it and the original post made that very clear!

We understand your frustration and really appreciate your reiteration on the feedback around the preserve scroll position feature.

We are glad you’ve kept an eye on the developments of this particular conversation and would simply like to reiterate our official position on the matter - we made the changes to preserve scroll position to make it more consistent.

Since our teams concluded that this was an intentional change (i.e. planned as a feature change internally) rather than an actual bug, we’ve solved the original topic (for that reason and that reason only).

However, we have been paying close attention to the community sentiment around this topic and are keeping our teams informed. Please let us know if you have any other feedback or arguments that you believe would help us strengthen the need to roll back the feature or further improve it.

Thank you for your understanding, we appreciate your collaboration.

@Figma_Support – What is most frustrating is you are making people dig through forums to figure out how to make this new feature work properly with their existing prototypes. Why is there not some sort of visual indicator that your Frames are not named correctly for this new feature to work? When the Frames that are not named correctly bounce and jerk around it sure makes it seem like a bug which is why so many people came here thinking it was…

Since we are forced to follow a naming structure, can the selection dropdown within the prototype interaction box be WIDER? I’m using short words and abbreviations and I still can’t see enough.

It is also frustrating that I can’t use the scroll wheel within this dropdown menu, and the interaction box appears all over the page instead of the old spot of a fixed position on the right.

@Figma_Support
To my mind, you can solve half of the troubles here by blocking the Y movement on an auto-layout frame used as a screen in the prototype. As you know, if scroll vertically is set to this screen, changing the size of a contained component will adjust the height of the screen too.

Defining the auto-layout height as fixed, solve a lot of bad reset scroll position behavior.

The origin of the auto-layout frame as screen must not move in prototype view.

As suggested, I have renamed all my top level frames. That didn’t work for me. Is there another work around? Because half my prototypes are unusable with click states being held hostage below the fold on smaller screens. This is crazy!!!