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
  • 24990 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

Design
May 26, 2023

You need to create variant to preserve scrolling position

Gaurav_Sharma2
May 26, 2023

I also faces the same issue since yesterday. @Figma_Support please roll back the feature.

Ryan_52
Figmate
Technical Quality Specialist
May 26, 2023

Hi all, if you are experiencing an issue we would like to take a closer look. Would you mind reaching out to our support team so they can assist further Submit a bug form →

May 28, 2023

same here… its super annoying

Masaoka_Shiki
May 29, 2023

Identical as in “with the same name” though.

Is that really the intended behavior? Feels like a bug because, at least in my workflow, it’s completely normal to have each frame named differently (“before click”, “after click”) and still want to have the scroll position preserved.

May 29, 2023

u can still have different frame names on your flow, but now you need to add dash ‘/’

for example ‘main menu / before click’ and ‘main menu / after click’.

Those are considered identical because figma only read the frame name before dash ‘/’

that rule is also written on the documentation

Masaoka_Shiki
May 29, 2023

Woot, that works!

Seriously had no idea about this. (But I’m a fresh XD refugee, so maybe that’s why…)
Thanks!

Eija_Vierimaa
May 29, 2023

Same thing. Prototypes break and start twitcing on interactions.

phroobin
May 29, 2023

I’m having the same issue here! The suggestion to make sure the top-level frames are named the same did seem to fix it, but it’s not an ideal solution when my frames are named separately for a reason… Hopefully we can get a fix for this!

Matheus_Freitas
May 29, 2023

I’m facing the same problems here guys! It seems to be more like a bug from this new update, to me you know. Like our friend @phroobin said, when we change the names of the frames to the same name, it works pretty well. But i’ve got 35 frames here dude, so we do need to give different names to identify those guys later. We all need to report this bug to the Figma Support, I guess. The more we all report, the sooner they will hear us and take a closer look at this issue. So let’s do it! 👍t4: