Skip to main content
Solved

Is there a way to get the prototype interactions of a nested component to run?

  • September 28, 2023
  • 2 replies
  • 837 views

I currently have a component (child component) that is nested in another component. The prototype interaction for that child component only have the “after delay” interaction. When that child component is used by itself, the prototype interations work just fine. However, the prototype interactions of that child component do not run/happen when it’s nested in the other component. Is there a way to get the child component’s interaction to run inside the other component?
I wish there was a way to get the component its nested in to “read” it’s interaction state, but I know that isn’t possible.

Best answer by Celine_

Hi Shelby!
Can you try to apply “Reset component state” to the interaction both to and from the modal to see if it can solve the issue? You can have more info on State management for prototype here: https://help.figma.com/hc/en-us/articles/14397859494295-State-management-for-prototypes Hope it helps!

If you need more assistance, we recommend reaching out to our support team with a copy of your file: https://help.figma.com/hc/en-us/requests/new.
Please invite support-share@figma.com with “can edit” permission, so they can take a look into this.

View original
This topic has been closed for replies.

2 replies

Celine_
Figmate
  • Community Support
  • 3680 replies
  • Answer
  • October 9, 2023

Hi Shelby!
Can you try to apply “Reset component state” to the interaction both to and from the modal to see if it can solve the issue? You can have more info on State management for prototype here: https://help.figma.com/hc/en-us/articles/14397859494295-State-management-for-prototypes Hope it helps!

If you need more assistance, we recommend reaching out to our support team with a copy of your file: https://help.figma.com/hc/en-us/requests/new.
Please invite support-share@figma.com with “can edit” permission, so they can take a look into this.


  • Author
  • 3 replies
  • December 12, 2023

I think what I actually had to do was to expose the nested instance, even though I didn’t want the interaction properties to be exposed, but this helped the prototype interactions be exposed in the component it was nested in.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings