Skip to content
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 instantly closes after update to Hero UI #4943

Open
G0razd opened this issue Feb 27, 2025 · 4 comments
Open

[BUG] - Navbar instantly closes after update to Hero UI #4943

G0razd opened this issue Feb 27, 2025 · 4 comments

Comments

@G0razd
Copy link

G0razd commented Feb 27, 2025

HeroUI Version

2.7.2

Describe the bug

Since updating to HeroUI, I have encountered a bug where Navbar will instantly close on first open, It will trigger the onMenuOpen function, if you remove the function it doesn't close, but the menu will not open, because of the way it is coded. This makes update to the HeroUI impossible for me.
Tested on Brave and in private window without extensions, issue persists. Doesn't happen on Mozzila, menu took a while and then loaded normally

Your Example Website or App

https://www.heroui.com/docs/components/navbar#with-menu

Steps to Reproduce the Bug or Issue

  1. On freshly loaded page click on controlled menu
  2. Menu will open and close
  3. Then click on menu again and menu will open normally
  4. Refresh page and start again.

Expected behavior

As a user, I expected menu to stay open, but it instantly closes on first open.

Screenshots or Videos

No response

Operating System Version

Windows, Brave Browser

Browser

Other (add additional context)

Copy link

linear bot commented Feb 27, 2025

@wingkwong
Copy link
Member

wingkwong commented Mar 2, 2025

I couldn't reproduce the issue in the doc on Brave (also other browsers). If the issue happens in your app, you may remove your node_modules and lock file and re-install again (the latest is now 2.7.4).

@wingkwong wingkwong closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2025
@G0razd
Copy link
Author

G0razd commented Mar 2, 2025

The problem still persists. I've tested this on multiple computers, so I have no idea why you couldn't reproduce the error. Perhaps I have described the problem poorly. In that case, I have provided a video of the issue on the doc page. This is running inside the OBS browser, and that also has the problem.

Platform:
Windows 11 Pro 22H2, Brave v1.75.181, Chromium 133.0.6943.141. Tested on other Windows PCs and Chrome browsers

This clearly isn't a problem with my specific machine; it is introduced in the HeroUI. This wasn't happening in NextUI.

Video link

@wingkwong wingkwong reopened this Mar 2, 2025
@wingkwong
Copy link
Member

Probably it only happens in Windows. Reopening it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants