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

Menu: Keyboard navigation broken in PrimeNg Diamond #13653

Closed
steveschmitt opened this issue Sep 11, 2023 · 1 comment
Closed

Menu: Keyboard navigation broken in PrimeNg Diamond #13653

steveschmitt opened this issue Sep 11, 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

@steveschmitt
Copy link

Describe the bug

Popup menu keyboard navigation works properly in the PrimeNg Menu documentation page

However, in the PrimeNg Diamond template, it does not work. Something is interfering with the keyboard events. We noticed this in our own Diamond-based app, but it is also apparent in the on the Diamond samples page. Click on Overlay Menu Options button and attempt to choose a menu item with the keyboard.

Environment

PrimeNG Diamond template
PrimeNG 15.3.0

Reproducer

No response

Angular version

15.2.6

PrimeNG version

15.3.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.12.1

Browser(s)

No response

Steps to reproduce the behavior

  1. Go to the Diamond samples page.
  2. Scroll down to Overlay Menu sample.
  3. Click on Overlay Menu Options button and attempt to choose a menu item with the keyboard.

Expected behavior

Menu should be keyboard-navigable as described in the Menu documentation

But the keys do nothing.

@steveschmitt steveschmitt 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 11, 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