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

SlideMenu - Cannot Toggle Popup When Hovered MenuItem Without Childs #13694

Closed
kkamay opened this issue Sep 18, 2023 · 1 comment
Closed

SlideMenu - Cannot Toggle Popup When Hovered MenuItem Without Childs #13694

kkamay opened this issue Sep 18, 2023 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@kkamay
Copy link

kkamay commented Sep 18, 2023

Describe the bug

Hello All,

As the title indicates, toggling functionality gets disrupted when a MenuItem without child items is hovered on a SlideMenu popup. This functionality works fine when the popup items are not hovered or the last item hovered is a MenuItem with child items. I have tried it by altering the StackBlitz that you have provided in PrimeNG website for SlideMenu popup.

Here is a video to show it to you better:
https://streamable.com/y4cbjw

Thank you.

Environment

PrimeNG Version: 16.3.1

Reproducer

https://streamable.com/y4cbjw

Angular version

16.2.0

PrimeNG version

16.3.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.20.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Open SlideMenu popup.
  2. Hover on a MenuItem without child items.
  3. Click elsewhere and see that the menu is not closed.

Expected behavior

Toggling functionality should stay the same for all elements (MenuItems with or without childs).

@kkamay kkamay added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Sep 18, 2023
@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. 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

2 participants