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
Row/SubRow selection not working as expected #3465
Additionally, it looks like if a subrow is indeterminately selected, its parent is NOT also indeterminately selected (but should be). "company" here is the parent that should be indeterminately selected as its child is.
This issue has been detected as stale and automatically closed. It's very likely that your issue has remained here this long because it would require breaking changes to v7. React Table v8 is currently in alpha (soon beta!) and already contains bug fixes, performance improvements and architectural changes that likely address this issue.
If your v7 issue has been previously labeled as requiring breaking changes, please try the new v8 alpha/beta releases
If your v7 issue has not already been labeled as a breaking change, open a new issue.
If this was a v8 issue and was closed by mistake, please reopen or leave a comment below.
Activity
dgattey commentedon Nov 30, 2021
I just came here to report the same bug - here's another CodeSandbox reproduction of it https://codesandbox.io/s/condescending-germain-lbn07. Thanks!
dgattey commentedon Nov 30, 2021
Additionally, it looks like if a subrow is indeterminately selected, its parent is NOT also indeterminately selected (but should be). "company" here is the parent that should be indeterminately selected as its child is.

dgattey commentedon Nov 30, 2021
#3106 This looks to be the same bug
github-actions commentedon Apr 8, 2022
This issue is being marked as stale (no activity in the last 14 days)
github-actions commentedon Apr 8, 2022
This issue has been detected as stale and automatically closed. It's very likely that your issue has remained here this long because it would require breaking changes to v7. React Table v8 is currently in alpha (soon beta!) and already contains bug fixes, performance improvements and architectural changes that likely address this issue.