You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without setting taborder via :pt, I found that children without children of their own are not present in the tab order. If those children contain tabbable elements like <a> tags, this appears to leave a jagged tab order.
We suggest checking the accessibility section of Tree component.
Tab key behavior: Moves focus to the first selected node when focus enters the component, if there is none then first element receives the focus. If focus is already inside the component, moves focus to the next focusable element in the page tab sequence.
Changing the tabindex of an inner element breaks all component behavior and keyboard support will not work as expected. We could suggest not changing the tabindex or creating your own Tree component in this case.
Describe the bug
With a
<Tree>
component that setstabindex
on the content via pass-through, pressing down arrow can raise TypeError:Motivation
Without setting taborder via
:pt
, I found that children without children of their own are not present in the tab order. If those children contain tabbable elements like<a>
tags, this appears to leave a jagged tab order.Reproducer
https://stackblitz.com/edit/primevue-create-vue-issue-template-qto7ki?file=src%2FApp.vue
PrimeVue version
3.50.0
Vue version
3.x
Language
ALL
Build / Runtime
Vite
Browser(s)
No response
Steps to reproduce the behavior
Expected behavior
No TypeError
The text was updated successfully, but these errors were encountered: