Skip to main content

I regularly create components that allow for easy manipulation of prototypes at scale. I can’t, however, use the “Scroll” to prototyping feature on interior elements of a component. I need to break the component which then removes the benefits of having it as a component in the first place.


Could we get it so scrolling to an interior element of a component is an option?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.


Hello Figma Community,

i am really new to figma. i am trying out my first prototype but stuck on my second day.


I build a sidebar component, where i can scroll the content and click some tabs to scroll down to the sidebar sections.

If i start the preview from the component it works as expected.

If i put the component to a page, where i will need it to use it more than once, i can scroll it, but the link interactions from the tabs don’t work anymore. (even the mousehand disappears)


Where is my fault? What did i forgot to check?

I would be happy if theres some help here.

Thanks a lot!!

Henning


Took a video for better understanding


Yeah I have the same problem here 😕

I think it’s a bug when it comes to nested components…


If not, I’m really missing something


Yeah, I have the same problem 🥲 @Figma_Support helppppp us


Figma Help Center

You can only scroll to top level objects.

When you try the sidebar on it’s own it works because the sidebar is the top level frame. As soon as you put it inside another frame, like when you put it inside the desktop frame, the sidebar is no longer the top level frame and scrolling stops working.


Please upvote! I am looking to reopen this previously closed request because I encountered this same issue recently. Scroll to point in component


This specific behavior feels like a bug because it allows you to create a component with scroll to triggers that worked before you make it a component – but then don’t work after you create it. It deliberately breaks all the links even though all the scrolling is encapsulated within the component itself.


I would rather have Figma tell me that a component cannot be created vs. creating it and not having the interactions work.


More importantly, fixing this would radically simplify some use cases where you have to make tons of variants to handle multi-state interactions. Simple scroll-to support would eliminate the need for so many variants (e.g. a large single-select radio button group).


This is particularly important for navigation. For instance, to create navigation to anchored links within a page, setting up scroll on a component is important so that you can use the same navigation across all of your screens.


See also the description of this problem here:

https://forum.figma.com/t/scroll-to-in-component-doesnt-work/19067


I have a component and set scroll to animation for that component. But it’s not working for the copies of that component. Any ideas?


I have a wide layer and a button in the component which scrolls to the last hidden right column.

When I bring the instance on the page scrollTO doesn’t work and there is no way to reset it or make a new connection.




I have 5 buttons that when clicked they scroll down to a section lower on the page. When I prototype it the scroll-to works, when I create a component out of the frame and view the prototype, the scroll-to works in the component.


The issue is when I copy and paste this component as an instance on another page or file. Not only does the scroll-to interaction disappear from the instance but you cannot use the scroll-to interaction within an instance. Seems like a bug, I have seen a few other reports in the community and nobody has solved it or offered a solution. Very frustrating that it works perfectly in the component but does not work nor allow new scroll-to interactions for the instance.


Yes, there are uncountable posts and feature requests about this issue:


https://forum.figma.com/t/support-scroll-to-within-a-main-component-instances-2022/29045

https://forum.figma.com/t/scroll-to-prototype-is-not-working-in-components/32678


https://forum.figma.com/t/scrollto-inside-component-doesnt-work-for-the-instance/34254


@dvaliao maybe it would make sense to reopen and merge them or something. I saw you did that with other posts aswell.


Thanks for looping me in, @Dennis_N!


We’ve re-opened and merged all relevant topics regarding this feature. We’ll pass this along to the team to review.


I also need this! I have a steps component where you open & complete each step individually. This is done in an interactive component. When the last step is finished and the user presses Send, I switch to the last variant which is a ‘completed’ variant. This variant is much shorter than each other variant (which all have a step opened). So I want to ‘scroll to the top of the component’. Currently I can’t do it so you will end up at the bottom of the page with the component completely out of view…


Still encountering issues with this?


You might be able to accomplish it inside the component itself by using the “Reset Scroll Position” feature they added.


Thanks for the suggestion Phil, but this doesn’t help. The interaction is within the component (it is an interactive component) and when I check ‘reset scroll position’ on the component interaction, it doesn’t help with resetting the scroll position in the parent screen that contains the instance.


You might be able to achieve the result then by moving the scrollable part of the experience to the component itself and it is just housed in a parent frame for prototyping. Then, you would have more control of the vertical scroll of the elements inside.


Reply