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
In the TreeTable Component, when I expand a row, in some cases the parent node gets selected (and therefore the @node-select event gets fired). I spent some time to reproduce this issue and after a while I found out, that this only happens, if the expansion action is done by clicking somewhere on the round expansion button/area (defined by "expander" tag on a Column) outside the "down-arrow" icon. So I feel like the issue is that the selection event is not properly bind to the whole click area, but only the icon itself. (See stackblitz)
Make a simple TreeTable with parent and child node and try to expand and collapse the child node. Check with @node-select when a selection is triggered and you will see that sometimes, expansion triggers it.
Expected behavior
On expansion, I don't expect the parent node to be marked as selected.
The text was updated successfully, but these errors were encountered:
Describe the bug
In the TreeTable Component, when I expand a row, in some cases the parent node gets selected (and therefore the @node-select event gets fired). I spent some time to reproduce this issue and after a while I found out, that this only happens, if the expansion action is done by clicking somewhere on the round expansion button/area (defined by "expander" tag on a Column) outside the "down-arrow" icon. So I feel like the issue is that the selection event is not properly bind to the whole click area, but only the icon itself. (See stackblitz)
Reproducer
https://stackblitz.com/edit/primevue-4-ts-vite-issue-template-fmv9y7dc?file=src%2FApp.vue
PrimeVue version
4.2.4
Vue version
3.x
Language
TypeScript
Build / Runtime
Vite
Browser(s)
No response
Steps to reproduce the behavior
Make a simple TreeTable with parent and child node and try to expand and collapse the child node. Check with @node-select when a selection is triggered and you will see that sometimes, expansion triggers it.
Expected behavior
On expansion, I don't expect the parent node to be marked as selected.
The text was updated successfully, but these errors were encountered: