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

Hi folks, if you’re still having issues with this the fix that I’ve been using is this: name your top level frames the same thing, but separate them by adding a slash and then the number in the flow. I.e. if I’m creating an onboarding flow, I’ll name it ‘onboarding / 01’ and the next frame in the flow ‘onboarding / 02’, which seems to have it working as before. It’s not ideal, but it’s better than nothing.

No idea why but it works. 😃
I just added a damn “/” in front of the numbers and it preserves the position again.
Thanks!

Have you found a solution for this? I’m having the same problem and you stated the problem best. I want Page B to MATCH Page A’s scroll position not remember it’s own scroll position. Please let me know if there’s a solution to this problem. I’m having this problem when I have tables with tabs and I want page B to match A’s scroll position without this jumping feeling.

This behaviour is indistinguishable from bugs and impossible to deduce from the UI. Well meaning users are going to break each others and their own protos constantly by giving frames useful names.

Seconding the comments here that the layer naming “solution” is not a solution. Pretty much every frame in a prototype is now resetting to the top. It’s very unintuitive to have to change that layer name on every single component that expands contracts, shows, hides, etc.

This is one of those moments where users decide to look elsewhere for a different product. The interaction cost for having to rename layers is extraordinarily high for something that could be a single-click selectable option. It’s also not heuristically obvious how to do this, even if it was worth the time (which it’s not), and is experienced as a bug. By stakeholders in presentations it’s viewed as sloppy design which reflects poorly on the designer.

Yeah, I’ve been reporting this issue since the change happened and despite Figma updates, still no proper fix!

This is beyond frustrating – something designers have to do every two seconds has a multi-point typing interaction and is completely unintuitive. It looks like most people still don’t understand how the solution works, even with the explanation. I have components expanding and contracting all over the place.

Totally agree!

We have an Organisation plan which has a big budget implication!

Sort it out Figma

For sure. This is one of those painpoints that’s existential for customer retention. They seem really happy with their solution though.