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
{{ message }}
Repository navigation
[v8] Row selection with sub rows has parent propagation issues #4298
When selecting sub rows there are some parent selection propagation issues:
When selecting a sub row with depth 3 then the parent is selected as indeterminate but the parent's parent is not selected
When selecting all sub rows (depth 3) of a certain parent then the parent selection changes from indeterminate to not selected instead of selected and the top-level parent is still marked as not selected
In the codesandbox (official react-table row expansion example):
Expand any top-level row and any child of the expanded top-level row
For issue 1): Select any leaf row with depth 3 --> Parent marked as indeterminate and the parent's parent still marked as not selected
For issue 2): Select all leaf rows with depth 3 --> Parent changes from indeterminate to not selected and the parent's parent is still marked as not selected
Expected behavior
As a user, I expected
for 1) that the direct and indirect parent rows of the leaf row that was marked as selected are marked as indeterminate (or selected depending on the data)
for 2) that the direct and indirect parent rows of the leaf rows that were marked as selected are marked as selected
but I am seeing that
for 1) the direct parent is marked as indeterminate but the indirect parent is marked as not selected
for 2) the direct and indirect parents are marked as selected
How often does this bug happen?
Every time
Screenshots or Videos
For 1)
For 2)
Platform
OS: Windows
Browser: Chrome (104), but also Firefox and Edge
react-table version
8.5.11
TypeScript version
4.7.4
Additional context
No response
Terms & Code of Conduct
I agree to follow this project's Code of Conduct
I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Activity
KevinVandy commentedon Jul 1, 2026
Looking at this now, the library is working as expected, but for the behavior you want, you just need code like this: