Skip to main content
Helge_Wadewitz
New Participant
June 13, 2022

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

  • June 13, 2022
  • 215 replies
  • 24993 views

Hey, i face a bug since there has been an update on the preserve scroll position behavior yesterday. By now the former preserve scroll position, which i had to set manually before is now set as default. So i don’t need to tick the box anymore.

But, in my protoype, although i expect now that the scroll position is preserved by default, it is not working correctly. From screen to screen my prototype is jumping to the top. I need to ship my proto today to the client and this is super annoying.

Anyone faces the same issue since yesterday? @Figma_Support can you roll back the feature? 🙏

215 replies

Livia_Biondino
June 22, 2023

This is so frustrating, I don’t understand why Figma would remove this option?! @Figma_Support is there anyway of getting this crucial option back? I have to present to a Senior Stakeholder tomorrow and this breaks the journey so much by shooting to the top of the page each time a link is clicked

Tamar_Ziri
June 22, 2023

it’s horrible and they don’t seem to care at all. is there anyone else we should be tagging besides @Figma_Support ? I’m sorry about your presentation

June 22, 2023

So glad I found this thread as I thought I was going crazy! I hope they get this fixed soon …

Gabriele.B
June 22, 2023

Please address this, it is so annoying. Prototypes with opening accordions are completely broken now. The only workaround I found is to have different “pages” with the same name, but it’s not something that can be done easily throughout a whole project.

June 22, 2023

Agreed! Please fix this Figma

RobW
New Member
June 23, 2023

This is the single most annoying bug/update that Figma has introduced. All my naming conventions are correct, yet this is still a problem. I have prototypes that no longer function as expected and I am losing confidence from stakeholders.

We need a fix or a rollback of this ridiculous update immediately.

Jorrell
June 23, 2023

It works! Thanks! Although I’m also not familiar with the dash (/) usage.

Grady_Mark_ESI
New Member
June 23, 2023

The naming convention fix only works if your page designs are wrapped each in a frame and the frame is named with the convention.

Even so, this is not a sensible or desirable way of working - for a company that makes the most used interface design tool in the world, surely your own primary UX rule should be “Users shouldn’t need to read the manual”?

Tia_Escobar
June 23, 2023

The new way this works with State Memorization requiring frames to be named the exact same is a problem when moving back and forth between page states. For a pricing page that has different product categories (business vs ecomm) and term lengths (monthly vs yearly) it makes clearly naming frames in the design file impossible. Is there a different way to do it? Can you add Preserve scroll position back?

john-mainboard
Active Member
June 26, 2023

At least tell us what is wrong and how to fix it upon opening the File and tell use how we can upgrade it, or do it automatically and add your /1 /2 after the frames.