Skip to main content
Jairo
May 19, 2021

Interactive components not working when nested inside a main component

  • May 19, 2021
  • 79 replies
  • 26998 views

Hello, I found out that if i create an interactive component (ex: Button), and place it inside a a main component (obsiously as an instance), the interactions are no longer working.
But if you create an instance of the parent component, then it all works as expected.

79 replies

Kevin_Hoffman1
October 28, 2021

I’m having the same issue. The variant interactions break when the child component instance is nested within another parent main component. However creating an instance of the parent component restores the interactions of the child component.

The existing workaround is to make sure you are navigating to component instances (not main components) when creating prototypes that require nested variant interactions.

Che
October 28, 2021

I have created a component like pills that have a close option, when I inserted in a filter component the auto layout is not at all working. Can you please help me? Thanks

Kris_Slazinski
October 29, 2021

I have the same problem. Interactive components are out of beta, but this seems still broken, unfortunately 😐

Bruno_HeroSpark
October 29, 2021

Same problem here 🥲

Jose_Augusto_dos_Santos
November 1, 2021

It’s a great deficiency that I’m not able to use the power of our Design system for interactive components.

It limiteds me in my daily work. I still have to switch to other prototyping tools.

I would like to use the full potential of interactive components by nesting them in other components. So I only have to set/design the interactive behavior once.

I’m curious why @figma hasn’t addressed this bug/feature yet?

Jaroslav_Kopecky
November 10, 2021

Similar problem for me. I am no table to cerate new working interactions on instances of variants component nested in main variant component. I can ceate interaction, but in Chnage To sectrion I am not able to change the variant. The value of property does not react on click attempt.

Simon_Lessing
New Member
November 10, 2021

Just wanted to add that it happens to me as well. Very confusing and somewhat hard to find, I spent quite some time before I understood what was happening.

Constantine_Zuev
November 16, 2021

Same here. I was hoping this was an issue with beta, but alas. This makes variant interactions completely useless feature. Virtually all basic building blocks that would benefit from having variant interactions are in turn used in other components. Checkboxes, radio buttons, dropdown menus – that’s what is typically #1 to be converted to component and used in other basic views… which are usually components too. Utter disappointment ☹

Constantine_Zuev
November 16, 2021

Update. Looks like this is some sort of nasty bug specific to pages.
I started from scratch. New document, no library etc. Created several components with variations. Created interaction within, wrapped them up in new several layers of other components. Everything just works! 🤯 I can click on checkbox and it switches on-off regardless of how deep it is nested.
The problem is, nothing works if I do exactly the same steps in my actual project file. Curiously when I created new page inside project file, there everything works. It seems as if variation interaction are disabled on old pages, regardless of what the settings says.

Marko_Kosovic
New Member
December 1, 2021

Still not working. @Jordan_Romanoff described it nicely — mouse enter / mouse leave / while hovering doesn’t work if nested inside another component. ☹