-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Navbar Mobile Menu Can Not Be Opened #4345
Comments
From my side, it works fine but i'm using Mac + Chrome tho. |
I'm getting the same on Windows 11 and Chrome Version 131.0.6778.109 |
Able to reproduce on Windows with Microsoft Edge. |
Mac And Chrome + Safari have same issue. |
I see the same BUG in their own site, and also my own... |
Weridly, the Pro version of this works just fine. So not sure why would the Pro version work and the regular one not... |
how to fix any one |
this appears to still not be fixed. Or at least not fully |
@macci001 please follow up |
I fixed it by removing onMenuOpenChange={setIsMenuOpen} from Navbar component and adding the press event handler directly to the NavbarMenuToggle component like this: <NavbarMenuToggle |
For me it's not working even after removing onMenuOpenChange from the Navbar. :/ I tries upgrading to 2.6.14, but it still doesn't work. |
yeah fro me its still broken too |
Well, for me it doesn't work at all. Not even after multiple clicks. It just "twitches" on the side of the page and immediately disappears. No error in the console. |
NextUI Version
2.6.8
Describe the bug
The mobile menu on the navbar cannot be opened. This issue is reproducible on the official documentation site.
Your Example Website or App
https://nextui.org/docs/components/navbar#with-menu
Steps to Reproduce the Bug or Issue
With Menu
section.Expected behavior
I expected the mobile menu to open and display the links, but the menu flickers and does not stay open.
Screenshots or Videos
NextUI-mobile-navbar-menu-bug.mp4
Operating System Version
Windows 11, Android 14
Browser
Chrome
The text was updated successfully, but these errors were encountered: