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

lost a half day’s work today thanks to this. And not working at all despite the workarounds suggested above. If anyone from Figma is reading this … here’s a golden rule for you: don’t fix what ain’t broke. I’ll be raising this with my team tomorrow as an example of extremely unhelpful UX ‘design’.

… still struggling with this, Figma folk … I am now going to have to postpone a whole week’s worth of scheduled UX Research testing due to this issue. This just to give you insight as to just how unhelpful this particularly bewildering ‘innovation’ to your experience is.

There are quite a few incredibly horrible things with this Update. When building frames for a sequence of screens. My agency and practice will Label the screens with an index number so that we can audit and see screen sequences in the layers panel. For example, if I have a login sequence we will name them Login-0.1, Login-0.1.1, Login-0.1.2, and so on and so on. We can no longer do this because all the screens have to have the same name in order for the Scroll position to remain in place. Or add a “/” between a name and an identifier. I can’t tell you how many prototypes are now completely ruined and will require someone to go in and manually correct screen names. And now that all my screens have the same name this makes it more likely that my design team will mess screens up when using the layers panel. HUGE MISTAKE ON THIS UPDATE. Thanks.

I am having the same issue.

In my POC you have to scroll down the web page to see a list of links — each styled as an individual frame. When I hover over the link I just want to show a simple smart-move interaction of the arrow icon in the link. In order for this to work I need the scroll position to stay put.

I have tried removing all of my nested frames so they are all stand-alone with no parent frame (before I had them all grouped in one parent frame like a section). These are not interactive components, not even components. They are just individual frames with a small move that I am trying to POC between two pages of a website on a hover.

As suggested, I renamed the 2 interactive frames that need to show this interaction so that they are named the same and are not sharing names with any other elements on the page. This is confirmed by the UI when I select one the other is highlighted.

And it still does not work.

This is perhaps the most simple type of spot-comp prototype I can imagine.

Please fix this fast or better go back to the what we had.

Please help! We still need the ability to preserve scroll function. This is an important piece of the design puzzle for prototyped components.

Yes! I don’t get why they changed it in the first place

Does anyone on the @Figma_Support team even reads these forums? it looks like they’re ignoring this… What needs to happen in order for an issue to be resolved? a certain number of votes? because that’s a bad metric to judge an issue by. Esp one like this that one must purposely google in order to find out that many many other people are having the same issue and it’s not something they did wrong. How many people need to virtually shout at you so you’ll fix such a major issue? I wonder how you people create your prototypes after this change since it takes about 5 seconds of prototyping to see how broken the scroll feature now is…

Related/Not-related. FWIW, I fixed my problem by removing the AutoLayout on my Frame.

Why? WHY? WHo asked for this?

Did you even test it before rolling it out?

@Figma_Support do you have any workarounds for us in the meantime, until you fix this?