Skip to main content

Just struck a pretty simple use case/scenario where I need the component to reset it’s state when I leave the frame. This has been touched on elsewhere, but this is such a common and key use that I thought I’d put it in it’s own thread.


Scenario:

I’ve got a dropdown menu with three items in it, with each item changing what columns are visible in a table and some other control states. I have three frames, each with a view of the table setup as it should be, and want to use the dropdown items to navigate between the frames - basically faking the table state change. All of this works perfectly, however when I navigate back to a previous table view state, the dropdown component is already in it’s open state - not what I want.


Current workaround: none that I can come up with (other than not using interactive components at all for this, and just using multiple frames for the dropdown open/closed states as I would previously)


Suggestions:



  1. Have a “reset component on leaving this frame” setting for instances of a component on a frame - useful for this situation and others, but needs to be a setting so that components that should keep their state between frames can do so (light/dark toggle maybe? Something like that).

  2. Do it all in a single frame, with the dropdown component changing the the state of the table component - no frame navigation required. Would work nicely for the particular use case I’m working with here, but not sure it would solve all similar situations.

  3. Do both 1 and 2. This solution is my preferred solution 😉 😆


EDIT:

Other threads that relate:


+1 this feature would be a blessing


This is a pretty basic function of prototyping and people have been talking about it here for two years.


+1 …I need to have a tiny animation that runs every time I enter a screen. My prototype is complex enough already, so always moving to a different Screen just for that is ludicrous.


I adore Figma, but I’m puzzled by this missing feature.


+1, lots of errors happen because of that on click and hover states for any library component because it falls back to the original component value


Please fix this March 2021- March 2023


+1, this would be a super useful tool even with some limitations


+1 for this feature! love to have this feature soon.


+1 for this important feature, great job to the team that provides so much improvements into Figma


Massive +1 🙏🙏🙏


Hoping this would be resolved by now! Seems like a very fundamental behaviour to be missing!!


Adding another comment here in hopes that more replies will lead to action from Figma. Pretty absurd that this hasn’t been addressed yet.


Wondering: can the OP @Emiliano_Cicero convert this topic to something we can vote on? I’m not sure if that functionality exists in these support topics. Worth a try?


+1 for me. Resetting Component States on Click would be so useful.


+1. Why is this feature taking that long? with the state management feature it would be a good timing. Its really important for making a good navigation Proto.


Hello rockstars. I have the tiniest question.


Context: I have a prototype with lots of frames representing UI states. Figma has made it very easy to wire up the prototype (some testers think it’s the actual app. ha! ). At various stages, I show progress bar components which simply use After Delay → Change To → Use Smart Animation.


The Issue: When a user arrives at a UI state, these Progress Bar animations play perfectly, but only the first time the user arrives at that frame. During their adventure, they may arrive at that same UI state many times, however…the component animation only plays the first time. Sometimes, the “After Delay” appears to begin counting when the prototype is started–not when the frame is loaded.


The Question: Am I totally looking at this wrong? Or is there a simple way to ensure these animated elements play correctly each time the frame is loaded.


Thanks in advance for any hints. 😃


+1, Adding another comment here in hopes that more replies will lead to action from Figma. Pretty absurd that this hasn’t been addressed yet.


Would really appreciate a fix for this… i’ve been going insane for the past few hours 🙃


Been a good two years now, guys. Planning on addressing this sometime this century?


+1. That would super useful Figma. 🙏


Come on, figma. I spent some hours trying to figure out this issue and found out that this issue has been here for two years?


+1 for fix


Need to add a +1 to this, working on a multi-selection component with select all/clear all button and obviously that falls into this case!


I have the exact same question. Any help is appreciated. Thanks!


Thank you all for your feedback!


Our team has confirmed that interactive components memorize their state “forcibly”, and there is currently no way to reset it.


Fortunately, this is already something they’re working on. While we can’t guarantee a timeline on our end, the team will continue to monitor this thread and use your Votes to ensure it’s prioritized.


Stay tuned and keep an eye on our Release Notes where we’ll post all major updates: https://releases.figma.com/


Thank you for replying, after all these years.


I think it’s important to understand that the lack of this feature (or the lack of thought behind how things “work” now) makes Figma inadequate for many prototyping situations, therefore the need to move to a different app for making it work.


Any workaround for this?


Reply