It is still without working. What can we do?

I’m seeing the same issue with hover states and am missing the option to “preserve scroll position.”

I have hover interaction low on my page and now in prototype, when I hover over that instance, it brings me to the top of the page. If I “roll-off” the area that the hover is connected to, it will bring me back to the original position of the non-hover state.

If I check “reset scroll position”, it makes it so there is no “roll-off” motion—it keeps me at the top of the screen with the hover state design activated (though you have to scroll to see it).

I was about to complain along with the original post, but as you mentioned adding the “name / subname” seems to work. Still, not intuitive at all. I can’t understand why complicate stuff that was already working for years.

Thanks!

Also missing this function when I want to “perserve the scroll location” when I jump between two wireframes. Worked before but since Reset scroll position and Reset componentstyle is the new option, I can’t find a way to get it working as before 😦

Thanks! It works!!

Seems that solution is that frames must have same name, and then by default scroll position will be reserved.

Yup that works for me too, but I agree that it’s not very intuitive though.

The same naming niether works for me.

Thanks for suggesting this fix, that seems to be helping for now. But I would expect the preserve scroll option to be brought back as an option, this took a few hours to figure out!

I have my frames/objects named the same between top-level frames, and they show up as the same object when I select an object in one of the top-level frames (indicated by purple outline on object in each top-level frame), but the scroll position isn’t being preserved properly when navigating back and forth - jumps several pixels in each direction. This worked much better in previous state management. Hope they fix this soon.

It is totally untenable/unworkable to have to name top-level frames identically to get prototyping working correctly. I shouldn’t have to conform my system for naming top-level frames to get prototyping to work correctly. This was NOT an issue or requirement in previous state management. And even when I do name them the same, the scroll position still jumps several pixels between frames.

Got to admit that the “name / subname” fixes things. So in a particular flow I just adjust name to “1 / current frame name” to keep things simple and not having to throw away my naming system.

Having the same issues as everyone else mentioned in this thread and prototype looks flawed. I need this to present to important clients but not in its current state. It looks unprofessional and clunky in and @Figma_Support needs to help sort this for everyone as soon as they are able?

Hi all,

Thanks for reaching out about this and our apologies for the disruption!

It sounds like you’ve run into some issues related to the limitations with the new State management for prototypes update, and for most users this is because the layers do not share matching names. In order for top level frames to share scroll state, they need to have matching names according to this rule.

=> Tips: for the frame naming, you can have different names but need to be identical before the ‘/’. (cf. screenshot)

If you are still running into issues after trying this, please reach out our technical team here.

Please also make sure to use your Figma account email, including a link to the file, and share it with support-share@figma.com as an editor on this file so the team can take a closer look.

Thank you!

I added them to my file, in there you can see on the “C/Services Active” flow the frames are named the same but will still have the scrolling position reset in the prototype 😦

Hi @tahannas ,

I can’t see your ticket in the backend. (feel free to share via DM the email you have sent your request, so I can double check 🙂).

Friendly reminder: please make sure to use your Figma account email, including a link to the file, and share it with support-share@figma.com when you reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new , so they can investigate. Thank you!

I am seeing the same issue, very annoying, has broken prototypes that were working perfectly.

Tried the same naming of frames as suggested and it still doesn’t work!

Please, please provide a fix asap!!

Same issue here. Frames have identical names and highlighted. But scroll position does not preserve.

Please fix it or roll back.

Only works if EVERY frame is the same. And I don’t like using frames within my designs (ie: button, dropdown, etc). Only for screens.

Why would you make this functionality only work if every frame is the same? What if I have 100 screens/frames in a prototype and instead of. wanting to link the screens on the design board, I’d rather choose the screen name in the prototype dropdown. I can’t do that because EVERY SCREEN HAS THE SAME NAME!

Try this.

1. Artboard should same file name.


2. Uncheck reset scroll position


3. Link your page


4. Good Luck!
   
   
   
   
   

@Figma_Support This is a disaster!! Roll back “preserve scroll position”

This new feature is not working at all. Have tried all kinds of tips and trix.

Honestly, this bug really sucks. Prototypes in general are buggy recently (noticing this over a month). I would really appreciate fixing this as soon as possible.

@Design Yes, if every page in my design is in a frame and has the same name then it works but that doesn’t make any sense to have it function that way.

Agreed, there’s clearly a bug here, no scrolling state is preserved with the new state management feature despite naming frames the same.

I’ve tried everything, as it seems everyone else has!

Please fix asap

Can u pls help me? Mine is still not working… i tried everything