Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 3.0, EE-3.0.0.BETA
-
Fix Version/s: 3.1.0.BETA2, 3.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 3.x
-
Assignee Priority:P3
Description
Code #1:
stateMap.setAllSelected(false);
Code #2:
for (Object rowData : stateMap.getSelected()) {
RowState s = stateMap.get(rowData);
//s.setSelectable(false);
s.setSelected(false);
}
The following code does show the rows as deselected, but they can't be selected again:
for (Object rowData : stateMap.getSelected()) {
RowState s = stateMap.get(rowData);
s.setSelectable(false);
s.setSelected(false);
}
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Problem lay with the selection and deselection occuring in the same request rather than the component. The table was using non-ajax selection, and the button to deselect submitted the form and decoded prior to the selection of the 'new' indexes.
The second half of the quote above appears to be in regard to a different issue. This issue doesn't concern dom diff.
However the first part is applicable. Implementing a client side deselect all by emulating clicks on the selected tr elements would be a future-proof way of solving this issue immediately at the application level.
ice.ace.jq('#dataTableWidgetId tbody:first > tr.ui-selected').trigger('click');
May very well be all that is required to deselect every row with a faux click.
Assuming the workaround is successful, marking this "Won't Fix" as resolving this from a product perspective would require implementing a complete client-side JavaScript API for the dataTable, which is out of scope for 3.1.
Test case that shows issue.
Steps: