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

Component: p-dropdown won't focus to next input when pressing tab key #13957

Closed
manutaitrmn opened this issue Oct 25, 2023 · 3 comments
Closed
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@manutaitrmn
Copy link

Describe the bug

When focused on a p-dropdown element with the "options" attribute defined, it is impossible to focus on the next input with the tab key.
However, when "options" attribute is not defined, it works.

Environment

Running node locally on my computer and use Angular / Primeng. The identified problem is only within PrimeNg/Angular.

Reproducer

https://stackblitz.com/edit/g27iot?file=src%2Fapp%2Fdemo%2Fdropdown-basic-demo.html

Angular version

16.2.10

PrimeNG version

16.5.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.2.10

Browser(s)

No response

Steps to reproduce the behavior

In the stackblitz :

  1. Click on the first input text.
  2. Press tab key to go to the first p-dropdown (with options attribute not defined)
  3. Once focused on p-dropdown, press tab key to go to next input text (it works)
  4. Once on input text, press tab key to go to the second p-dropdown (options attribute defined)
  5. Once focused on the second p-dropdown, press tab key to go to last input text
  6. Blocked, it stays focused on the p-dropdown

Expected behavior

From the second p-dropdown focused, when pressing tab key, it should focus on the next input text.

@manutaitrmn manutaitrmn added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 25, 2023
@lslocumwrb
Copy link

I am experiencing the same issue after upgrading to 16.5.0

@AlexisDefranoux
Copy link

Same on 16.3.1

Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response 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