1. While creating a clickable prototype, I want to enable a button to take the user to a specific scrolled position on another frame/ artboard. Currently, I can only use the “scroll to” feature if it is within the same page.

Would it be possible for the Figma team to solve this by having an added interaction called “Navigate to scrolled position” and allow the user to connect from an item in one screen to another item in a different screen? The prototype would then seamlessly shift between screens and incorporate scrolls.

Screenshot 2021-08-20 at 2.50.08 PM|379x345

Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?

+1 to this - @figma is this being considered?

Yes I’m having the same issue 😦

@anon21722796 Is this feature going to be added? It would be great to link to a specific section in another page vs. just the default top. Let me know. Thanks!

Hello! Was this issue ever solved for? Thank you!

This is a crucial feature! Mobile sites don’t have space for full navigations and require the hamburger menu overlay. How else can one prototype a mobile single-page site?

When is this feature being added?

A work around would be to navigate to the other page(make another copy or else the original page will scroll) and scroll to position from there after delay

That’s what I did lol, but the problem is that I won’t be able to click on that anchor link and scroll again since I am already on that copied page, you don’t want your original page to scroll

Hello, have you tried the after delay interaction? It could solve the need. Once the frame loads (100ms) you can scroll to a specific layer. Good luck!

Hey Team! ANY chance this is a feature you’re considering yet?

Hey Figma team! This would be great if you fix this! 🙏

+1 to this, this comes up quite a bit when designing for mobile website screens

Another +1. This would be really helpful if Figma can add this to the next update!

PLus one to this

+1 for this feature.

I’d love that… miss my old rp.

I’m overwhelmed for this, because it one of the “basics” elements of navigation. I just can’t fit in me

+1

Yes, can’t believe this basic function is not a part of the app.

Soooo miss Axure!!!

+1 I really need this!

Actually got this sort of working by copying the menu (with working interactions to Scroll To frames in its own page) to another page… then combining ‘Click’ and ‘Mouse down’ interactions to allow both Navigate To and Scroll To on mouse click… but as soon as I removed the interaction I could not readd it. I think it’s not intended behavior 🙂 Would be very nice to have one single ‘Navigate To ____ and on that page, Scroll To ____’ interaction.

+1 This would be very useful!!

+1+1+1+1+1+1+1+1+1+1+1 for all our sakes.

+1 Pleeeeease !!!

+1 this would so helpful and save so much work creating clunky workarounds.

We are still waiting for this? 🤯

+1 as many as it takes.

Please add this I am trying to create a very simple site prototype and cannot connect to specific page sections from another page 😦