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

Multiselect: Scrollable region must have keyboard access #16225

Open
TaneliTuomola opened this issue Aug 14, 2024 · 0 comments · May be fixed by #16226
Open

Multiselect: Scrollable region must have keyboard access #16225

TaneliTuomola opened this issue Aug 14, 2024 · 0 comments · May be fixed by #16226
Labels
Status: Discussion Issue or pull request needs to be discussed by Core Team Status: Pending Review Issue or pull request is being reviewed by Core Team
Milestone

Comments

@TaneliTuomola
Copy link

Describe the bug

When scanning the multiselect component with axe Devtools you will get the following error:
image
There was a same issue with the dropdown: #15155
And this is duplicate to the already staled issue: #15003

Environment

PrimeNg 17.18.8

Reproducer

https://primeng.org/multiselect

Angular version

18.0.1

PrimeNG version

PrimeNg 17.18.8

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.12.0

Browser(s)

Chrome

Steps to reproduce the behavior

Open multiselect with scrollable content and run axe Devtools.

Expected behavior

No response

@TaneliTuomola TaneliTuomola added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Aug 14, 2024
@cetincakiroglu cetincakiroglu added this to the 17.18.9 milestone Aug 15, 2024
@mehmetcetin01140 mehmetcetin01140 modified the milestones: 17.18.9, 17.18.10 Aug 15, 2024
@mehmetcetin01140 mehmetcetin01140 modified the milestones: 17.18.10, 17.18.11 Sep 11, 2024
@cetincakiroglu cetincakiroglu modified the milestones: 17.18.11, 17.18.12 Sep 26, 2024
@mehmetcetin01140 mehmetcetin01140 modified the milestones: 17.18.12, 17.18.13 Nov 13, 2024
@mertsincan mertsincan added Status: Pending Review Issue or pull request is being reviewed by Core Team Status: Discussion Issue or pull request needs to be discussed by Core Team and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Nov 18, 2024
@mertsincan mertsincan modified the milestones: 17.18.13, 17.x Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Discussion Issue or pull request needs to be discussed by Core Team Status: Pending Review Issue or pull request is being reviewed by Core Team
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants