Skip to main content
Question

Scroll-to interaction not working

  • June 24, 2022
  • 10 replies
  • 3390 views

Ilija

Here’s a link to the prototype that presents the bug in question

Figma – 24 Jun 22

I cannot make either the main component nor the child of the component ‘scroll to’ top nor bottom.

My goal is to have a parent component with interchangeable content in the middle, with two buttons for scrolling to top and bottom, so that when I make child components and change the content in the middle the functionality of scrolling to top and bottom still works.

When I’m using just frames for everything, then everything works fine.
But, as soon as I make a component the ‘scroll to’ buttons stop working.

I also tried making the content height ‘hug’, but the behaviour doesn’t change.

Why doesn’t ‘Scroll to’ interaction on buttons ‘Top’ and ‘Bottom’ work?

10 replies

j.liu
  • 2 replies
  • May 25, 2023

Same problem here. I also encounter this when I try to make an affter-delay animation with scroll-to interaction.
When I detach the instance(make it into normal frame), the scroll-to works fine. But the original component just doesn’t seem to react to scroll to interaction.


Alena_Keln
  • 1 reply
  • August 29, 2023

Also have the problem. If you examine the component and want to reconnect the functions with “scroll-to” this is also not possible, because you can not select the layers. Seems to be a bug to me. If it is not inside a component, scroll-to works fine.
I built a media carousel component with the function, which unfortunately has to be detached every time before it works.


Harun_Alikadic1
  • New Participant
  • 13 replies
  • October 29, 2023

Same here. I am trying to make some After delay “scrolls to” for a component with vertical scroll enabled. When the component is embedded into a frame it should showcase automatical scrolling in a card to a specific content. If the component itself is launched in a presentation, it works, but embedded in a frame, not.
I am not sure if this is a bug or by design?


djv
Figmate
  • Community Support
  • 5211 replies
  • November 7, 2023

Hey All, sorry to hear this is happening. Please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new

Be sure to use your Figma account email, include a link to the file, and share it with support-share@figma.com, so they can take a closer look.


Gerard_Pamies1

Same problem here. Scroll-to works fine as long as not being inside a component. The component works correctly but the instances are not working properly


James_Touhey
  • New Member
  • 3 replies
  • March 4, 2025

I’m having the exact same issue (Now 2025). I set up several scroll-to actions and tested them working as expected, but after making it a component, the actions are lost.


y_toku
Figmate
  • Community Support
  • 2544 replies
  • March 5, 2025

Hi ​@James_Touhey 

 

Thanks for flagging this. I’ve reported this issue with our internal team.

I will get back to you when I have anything I can share with you. 

 

Thanks for your patience.

Toku


Marek Grodzicki

I’m having the exact same issue (Now 2025). I set up several scroll-to actions and tested them working as expected, but after making it a component, the actions are lost.

What actually happens is that the instance interaction points to the element in the source component rather than its instance. That makes scrolling to an element that doesn’t belong to the instance or even to the same set of nested frames/objects impossible. The only way atm is to detach component and add actions manually. But then if you want to update the component, you will need to repeat the detach>define process every time.


Magdalena UXUI
  • New Member
  • 1 reply
  • June 16, 2025

June 2025 and the same problem STILL happening… Pls fix this :/ 


Luke Manimala
  • New Member
  • 2 replies
  • August 21, 2025

+1 This is still broken.

Can’t add the scroll interaction on a component only on non-components. This is a bummer especially if nesting component content sets into large components.

Makes it hard to scale multi-page components/interactions