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

p-megaMenu: Menu opens automatically on mouse hover #16081

Closed
VF9999 opened this issue Jul 23, 2024 · 3 comments
Closed

p-megaMenu: Menu opens automatically on mouse hover #16081

VF9999 opened this issue Jul 23, 2024 · 3 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@VF9999
Copy link

VF9999 commented Jul 23, 2024

Describe the bug

When hovering the mouse over a p-megaMenu component, the menu opens automatically. All mouse hover settings in Windows have been turned off and all menus and links open when clicked except p-megaMenu, which opens on mouse hover.

Environment

Windows. Angular development.

Reproducer

No response

Angular version

17.2.3

PrimeNG version

17.10.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.20.4

Browser(s)

Chrome 126.0.6478.183, FireFox 128.0

Steps to reproduce the behavior

  1. Hover mouse over p-megaMenu component and the menu opens without clicking it.

Expected behavior

When clicking the p-megaMenu, it should then open.

@VF9999 VF9999 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 23, 2024
@rosenthalj
Copy link
Contributor

See the following closed Issue #14086: MegaMenu & MenuBar | Activate root item on hover

@wendannor
Copy link

Would it be possible to adjust the configuration of the megamenu to trigger its opening upon a click event, rather than upon hovering ?

@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation and try the latest PrimeNG version(v19). If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

4 participants