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

Cannot tab into tieredmenu where an id and label exist #14638

Closed
Cue-Ai-NGinEar opened this issue Jan 26, 2024 · 1 comment
Closed

Cannot tab into tieredmenu where an id and label exist #14638

Cue-Ai-NGinEar opened this issue Jan 26, 2024 · 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

@Cue-Ai-NGinEar
Copy link

Describe the bug

Unable to tab into an element within the p-splitbutton component. This only happens when you have a value set for optional parameters "label" and "id" - if you remove the id parameter then you can tab into the tieredmenu element.

Environment

Angular app running in Chrome.

Reproducer

No response

Angular version

16.2.9

PrimeNG version

16.9.1

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

18.19.3

Browser(s)

No response

Steps to reproduce the behavior

Within the p-splitbutton component, if you tab to the defaultbutton, then menubutton and active this, you cannot tab into the tieredmenu - it is impossible to get the keyboard to focus into the menu.

Expected behavior

You should be able to have an "id" value set on the tieredmenu element with the p-splitbutton component and still tab into it.

@Cue-Ai-NGinEar Cue-Ai-NGinEar added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 26, 2024
@mehmetcetin01140
Copy link
Contributor

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