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-menu w/ popup: enter key on number pad doesn't select menu item (accessibility issue) #15415

Closed
Da13Harris opened this issue Apr 30, 2024 · 0 comments · Fixed by #15428
Closed
Labels
LTS-16-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@Da13Harris
Copy link

Describe the bug

There are two enter keys on most standard keyboards, one next to the alphanumeric keys and one next to the number pad.

Using a standard <p-menu [popup]="true">, you can trigger an item using the primary enter key, but you can't when using the enter key on the keyboard's number pad.

Environment

Windows 10, but this occurs in any environment, including Stackblitz and the PrimeNG website.

Reproducer

https://github-mgg3my.stackblitz.io

Angular version

17.3.6

PrimeNG version

17.15.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.1

Browser(s)

No response

Steps to reproduce the behavior

Using the menu in the supplied StackBlitz reproduction, you can select an item using the primary enter key, but you can't when using the enter key on the keyboard's number pad.

Expected behavior

The enter key on the keyboard number pad should trigger menu options, just like the standard enter key does.

@Da13Harris Da13Harris added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 30, 2024
@cetincakiroglu cetincakiroglu added this to the 17.16.0 milestone May 2, 2024
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working LTS-16-PORTABLE and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LTS-16-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants