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
If you are doing a sever side render with selected rows and have selectToolbarPlacement set to 'above' when you do something like search, filter or sort the selected rows should be unselected as that Item might not be in the response. Might want to update the onTableChange to have set state options so user can reset table state of thing if needed.
Current Behavior
If you are doing a sever side render with selected rows and have selectToolbarPlacement set to 'above' when you do something like search, filter or sort the selected rows index is still selected. So if I select the first item an sort by name the first item of the few results is still selected .
Steps to Reproduce (for bugs)
set serverSide: true
set selectToolbarPlacement: 'above'
select a first row
sort by column header
selected-row-bug.mp4
Your Environment
Tech
Version
Material-UI
^5.1.0
MUI-datatables
^4.0.0
React
^17.0.2
browser
all
The text was updated successfully, but these errors were encountered:
Expected Behavior
If you are doing a sever side render with selected rows and have
selectToolbarPlacement
set to 'above' when you do something like search, filter or sort the selected rows should be unselected as that Item might not be in the response. Might want to update theonTableChange
to have set state options so user can reset table state of thing if needed.Current Behavior
If you are doing a sever side render with selected rows and have
selectToolbarPlacement
set to 'above' when you do something like search, filter or sort the selected rows index is still selected. So if I select the first item an sort by name the first item of the few results is still selected .Steps to Reproduce (for bugs)
serverSide: true
selectToolbarPlacement: 'above'
selected-row-bug.mp4
Your Environment
The text was updated successfully, but these errors were encountered: