Skip to main content

Hi all,


I am experiencing an extremely weird (seemingly) prototype behavior and I would like to find out if that could simply be a Figma glitch that will resolve itself in time.


I am sorry to say I can’t publicly share the project, but I’ll try to explain.


Here’s the setup:



  • A header component (with a burger to show/hide menu)

  • A menu component

  • A wrapper component that wraps the menu and the header components (to deal with responsivity, i.e., to have the menu stretch to the height of the page)

  • The wrapper component is what I use in my screens, and it has two states - menu open and menu closed.


Here’s the problem:



  • My homepage has a ‘Button’ (not in the menu) that links to a different screen/frame.

  • My menu has a ‘Home’ button that leads back to home screen/frame.



  1. When I press the ‘Button’ for the first time, it simply goes to the respective screen - as expected.

  2. When I open the menu and hit ‘Home’, it goes back to home screen - as expected.

    3. When I hit the ‘Button’ for the second time, it does go to the respective screen BUT the menu changes its’ state to open


Reset component state has no effect on the problem. Mobile app, desktop app or web has no effect on the problem either. However, if I reach the home by different means (say breadcrumbs), the problem doesn’t occur. Any ideas why is that? 😦

I kind of managed to find a solution, though I fail to make sense of it.


Besides what I wrote, I also had a mobile/desk variants for the wrapper component, and the toggle was attached to a variable. Breaking the link to the variable fixed the problem.

Reply


Terms & ConditionsCookie settings