@Cricitem thanks! You’re wicked. That solved the issue with clicking behind the form.
I’m still having troubles with the hamburger interaction. It is bugging out and shows an X even when the menu is closed if you click on one of the navigation links.
Just put an interaction on each nav link that animates your nav burger to the correct state. I believe right now you only have that set to if a person actually clicks on the nav burger itself.
EDIT: Actually, I didn’t realize you had that animation tied to click events on the hamburger icon itself. Just tie the animation to the navigation dropdown open and close and you should be good to go.
Where you select the trigger for the interaction, instead of “Click” choose “Dropdown”. That will give you a window with two triggers, open and close. Do the same animations you did for first and second click in there, and remove the click animations. That should take care of it.
You are going to replace each with a Dropdown trigger. If you go into each of those Click events, you’ll see a “First Click” and “Second Click” trigger. You just translate each of those into a “Open” and “Close” Dropdown trigger (respectively).
Did you clone this from somewhere? I’m kind of surprised it wasn’t done as a Dropdown trigger in the first place.
It has something to do with that element. I put another dropdown list on that same page and applied a dropdown interaction to it, and it worked. I can’t apply ANY dropdown interaction to that element. It looks like it’s because it was originally created as a menu button instead of a dropdown toggle (even though it functions exactly the same way and even has a “drop down” function in its settings), so it isn’t recognizing the dropdown state.
I believe this is a bug. You would need to recreate the menu specifically as a dropdown instead of being a menu button. Everything else would remain the same, with dropdowns instead of click events. Whoever did it that way was not thinking ahead or didn’t mean for the button to be used this way.
