"Scroll to" objects in different frames

+1, for now I am using @Francois9 tip.
but maybe can work with conditionals. Any tips? Maybe @Gleb will know who to ask. 🙏

Please add this option!

+9000 for this feature

The only way to achieve most of these basic interactions that are missing in Figma is through workarounds. You can use the delay approach, or you can modify the layout of the second frame so that the area you need to see is in view. Make sure the frame has vertical scrolling enabled so that users can still scroll back up or down from that location to view the other content.

Figma has never been a good prototyping tool unfortunately. The dev team keeps adding features that no one wants while ignoring the stuff that designers actually need to be able to create true-to-life prototypes. For this reason, the company I work for has a Figma design system and we import to Axure whenever advanced prototyping is needed.

+1 to adding this feature please!!

+1 

+1

Yeah but then Page 2 must be only dedicated to that. (opening from Page 1)
If you have other links in other pages that open Page 2, then it will also scroll.
You’ll have to create a specific Page2-fromPage1.

or

Using variables, but that’s a really complicated solution for such a simple problem.

PLEASE let us select a specific target element on a different frame, when using the Navigate to interaction.

+1 (and +50 of my students) to this! This is a well needed feature! Please consider it Figma team! 

Workaround

1. Copy/Cut the element where you want to use the prototype action: scroll to.
2. Paste it to the page which contains the scroll to target
3. Configure the scroll to prototype action on the element - the target can be selected now
4. Copy/Cut the element from the target page and paste it back to the original page. The target from the other page is still in place (disabled in the pulldown though).
5. Note you may need to (re) configure the navigate to action if that was in place before.

I use this trick to make my components interactive (navigate to), even if they are on a separate page in figma.

I think this works because Figma stores the configured values, even if they are not selectable anymore in the UI. Hence the disabled values after pasting them back.

Rant:

Hey Figma, maybe stop developing the next side-hustle to make wallstreet happy and improve the core product? Runner-up, maybe the lowest hanging fruit: hover, active, ... states. Text links that hover:underline without crappy text components – CSS/HTML is rad, you know!??

Also: maybe start putting some people here to react on 4 year old posts (I have actually seen much worse here on other quirks).

You know what this reminds me of? JIRA/Atlassian. They also do have 16-year-old posts (I am not joking) without a solution to the problem … inside their own public support JIRA.

Come on Figma, you can do better.