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
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [5007000000LEHrf] |
| Attachment | Case11018Example.zip [ 14109 ] | |
| Attachment | Case11018ExampleWAR.zip [ 14110 ] |
| Assignee | Nils Lundquist [ nils.lundquist ] |
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.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Invalid [ 6 ] |
| Fix Version/s | EE-3.0.0.GA [ 10262 ] | |
| Fix Version/s | 3.0.1 [ 10282 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Resolution | Invalid [ 6 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
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.
| Assignee Priority | P3 |
| Fix Version/s | 3.1.0.BETA2 [ 10336 ] | |
| Fix Version/s | 3.1 [ 10312 ] | |
| Fix Version/s | EE-3.0.0.GA [ 10262 ] | |
| Fix Version/s | 3.0.1 [ 10282 ] |
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.
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Test case that shows issue.
Steps: