Hello, I would like to get help on two issues I am having with the navbar.
The first is that there is an interaction for the navbar to disappear and reappear on scroll, but it is not working on every page. I don’t understand how to fix this. The navbar is a component and is placed on every page.
The second issue is how to get the mega menu to stay open when the user moves off the hover link? It’s going to be difficult to explain in words, but the mega menu slides down but if the user moves the cursor diagonally to reach the links, it closes. The menu only stays open if the user moves the cursor down and then moves within the menu. But I would like it to stay open longer to give people a chance to click on the items in the menu. Our site visitors are not computer savvy and would be confused by the way the menu closes so quickly. The mega menu was added from a library, so I’m not quite clear on how to customize it.
Pet peeve of mine but I can’t deal with hover-driven mega menus. I believe these offer a poor user experience since things happen that are not user-initiated. I’d switch it to a click
I’m not seeing the navbar disappear/reappear interaction at all. One easy way to implement this is to use the Page Trigger > Page Scrolled and tell the nav to move up an out of the browser when scrolling down and then move down into view when the user scrolls up.
This would apply on each page using a component and applying it to the Desktop Navbar class.
Thanks so much for your reply. Here is a link to one of the pages where it is working.
The page scroll trigger is on the component itself, so I don’t understand why it’s not working on every page. I’m not sure how to fix it. I’ve redone it many times and that does not fix the problem.
Excellent.
Using the homepage as an example, if you check out the Interactions panel, you’ll notice that the page trigger is not applied. You’ll just apply the interaction on each of these pages.
Let me know if you have trouble.
Thank you! I didn’t know it needed to be on each page. I thought it was linked to the component itself. I truly appreciate your help. I spent so long trying to find the answer.
Very grateful for your help.
