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
Describe the bug
If the MultiSelectHeader checkbox of the SelectionPlugin is checked, currently it is staying checked even when no table rows are checked after a change.
This is observable using LocalListDataStore.setData (where the table data is refreshed and table rows are re-added unchecked), and also using pagination where the selected rows get unchecked when changing pages.
See error, no table entries are checked but the header checkbox is still checked.
Expected behavior
Header "Select all" checkbox should not be checked if not all table rows are checked
Screenshots
Before changing page:
After changing page:
Additional context
If the Header Checkbox would be somehow accessible, it could be unchecked manually but it is directly appended as a HTMLElement in the SelectionPlugin, and controlled via a changeHandler and a datatable-SelectionListener (V1, haven't checked V2 yet).
The text was updated successfully, but these errors were encountered:
looks like the recent changes to SelectionPlugin created a bug. if multiselect is true, it works fine. if multiselect is false, then SelectionPlugin#updateHeaderCheckBox() crashes on lines 330 and 332 because headerCheckBox is null
Describe the bug
If the MultiSelectHeader checkbox of the SelectionPlugin is checked, currently it is staying checked even when no table rows are checked after a change.
This is observable using LocalListDataStore.setData (where the table data is refreshed and table rows are re-added unchecked), and also using pagination where the selected rows get unchecked when changing pages.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Header "Select all" checkbox should not be checked if not all table rows are checked
Screenshots


Before changing page:
After changing page:
Additional context
If the Header Checkbox would be somehow accessible, it could be unchecked manually but it is directly appended as a HTMLElement in the SelectionPlugin, and controlled via a changeHandler and a datatable-SelectionListener (V1, haven't checked V2 yet).
The text was updated successfully, but these errors were encountered: