[ https://issues.jboss.org/browse/RF-10793?page=com.atlassian.jira.plugin.s... ] David Lee commented on RF-10793: -------------------------------- Hi Guys, The fix JavaScript will cause another issue, if the table with dataScroller -- then the selection will be clean up when user switch the page. So since I have the page stuff, I cannot add the "x" to do clean selection in backend. When I try to figure out why the statement always goes wrong, I found the key of this problem might in TableSelectionRendererContributor.java: for line 90 ClientSelection _oldClientSelection = (ClientSelection) table .getAttributes().get(CLIENT_SELECTION); << The _oldClientSelection never got update, so when the code checking for shouldRemoveFromSelection(), always return false! // Decide whether to remove new row to selection based on comparison with // old one public boolean shouldRemoveFromSelection(int i, ClientSelection oldSelection, ClientSelection newSelection) { return !newSelection.isReset() && (!newSelection.isSelectAll() && (!newSelection.isSelected(i) && oldSelection .isSelected(i))); } << The oldSelection.isSelected( i ) always return false. That cause the backend selection goes wrong. Any workaround for this one? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira