Attached test case.

Steps:

• Load welcomeICEfaces.jsf
• In Chrome, click on a checkbox button. The row will be selected and the check will be cleared.
• In Firefox/IE11, click on a checkbox button. It will be checked. Now select the row, the check will now be cleared.

Added similar test cases with ACE Input and Button components.

Passing tests:
Input Components (ace:textEntry, dateTimeEntry, textAreaEntry, maskedEntry, autoCompleteEntry, sliderEntry, colorEntry): /ICE-11223b.jsf - test appears to pass in all browsers (Chrome, MsEdge, FF49, IE11): the row selection does not change after entering/selecting text and pressing TAB/Enter.
Note, ace:autoCompleteEntry passes only if selecting autoComplete options using the keyboard.

Issues found:

1) ace:pushButton: /ICE-11223a.jsf
Test passes on Firefox49 and IE11, and it fails on MsEdge38, Chrome55 and Safari: pressing the pushButton changes the selected state on the row.

2) ace:richtextEntry: /ICE-11223c.jsf - this test fails, the rows become selected after saving text in the ace:richTextEntry.
Also, in Chrome, a JS error occurs when clicking the "Save" icon:

ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:340 Uncaught TypeError: Cannot read property 'on' of undefined
at $.attachListener (ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:340)
at $.setup (ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:351)
at $.m (ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:829)
at ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:28
attachListener @ ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:340
setup @ ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:351
m @ ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:829
(anonymous) @ ckeditor.js.jsf?ln=icefaces.ace&v=4_2_0_170126:28

3) ace:radioButtons: /ICE-11223.jsf
Test fails in the same manner as ace:checkboxButtons:

• in Chrome/MsEdge, when clicking a button the row will be selected and the check cleared.
• in FF/IE11, when clicking the button, it will be checked; when selecting a row, the check will be cleared.

4) ace:menuButton: /ICE-11223a.jsf
Test fails in all browsers, selecting a new menuItem changes the row selection.
In MsEdge/Chrome, clicking the menuButton also changes the row selection, and the menuButton fails to open up and render its menuItems.

5) ace:autoCompleteEntry /ICE-11223b.jsf
Test fails in all browsers if selecting the autoComplete options with the mouse, the row selection changes in this case; the row selection does not change if using only the keyboard keys.

6) ace:buttonGroup: /ICE-11223a.jsf
Test fails only in Chrome/MsEdge: selecting a radioButton or checkboxButton inside the buttonGroup changes the selection state of the row.

Fix filtering of elements that can trigger a row selection. This blocks 'click' events triggered by components located in the data table cells to select/deselect a row.

Tested with ICEfaces4 trunk r50353 in MsEdge38, Chrome55, FF49, IE11:
Issues 1) to 6) above have been resolved.

On /ICE-11223.jsf: when clicking a checkbox button/ radio button, it will be checked, but selecting the row will clear the button selection.
This behavior is now in all browsers, is it expected?

Q: This behavior is now in all browsers, is it expected?
A: No, it's not. It seems that this is not a component issue. I modified ICE-11223.jsf page to have the checkboxes and radio buttons AJAX submit their state changes thus any incoming updates will not change the state on the client.

This fix needs to target focussable input elements, not all elements.

Run double/click callbacks whenever the data table cell is double/clicked or any of it children. Previously only double/clicking the cell or the first child of it would have run the callbacks.

Exclude child input elements from triggering a cell edit or row selection.

Re-opened to block input comps from activating row selection.

Input elements are now blocked from activating row selection.

I don't see the original issue reappearing. I used both the attached test case and dataTable/ICE-11223.jsf, they work as expected.

Modified datatable.js to have the 'click' and 'dblclick' events blocked from reaching the data table cell when they bubble through an input elements.

Fixed linkButton and menuButton issue by adding the anchor element to the list of element types that block event bubbling.

I cannot reproduce the issue with richTextEntry. I used Chrome for testing.

Fixed autoCompleteEntry by wrapping the matching results in an anchor tag (replacing a DIV) so that the dataTable cell will detect itand block the event bubbling.

I cannot reproduce the 'Missing resources for "ColorEntryInit" component.' JS error.

Removed rogue comma to allow for colorentry.js compression to complete successfully.

The colorEntry issues above are resolved at r. 50772, however the test fails, as the row gets selected/unselected when clicking on the colorEntry outside of the color selection rectangle (all browsers).

So long a the user clicks on an focusable element inside the color selection pane it works as expected, however, it is possible to trigger the row selector if clicking in side the pane in a whitespace area. This is a side-effect of how this must be implemented and isn't particularly harmful, so we'll consider it an acceptable known issue.

It might be possible in the future to have the dataTable logic also check for the presence of a marker css class on an element which would tell it to ignore clicks from inside the element. This would provide a mechanism to avoid this.

reopened for Support Case 14185 to backport fix to ICEfaces 3.3.0 maintenance branch

r51869: backported all fixes to the 3.3 EE maintenance branch

Testing Notes: The last test case added (the one using ace:checkboxButton instead of ace:checkboxButtons) needs to be added <ace:ajax /> to the ace:checkboxButton, in order to save the checked state, otherwise, it's just a client-side component and the state is lost after selecting a row.

Please also run all ace:autoCompleteEntry tests, since there was a modification for this fix to work.

It's important to mention that for this test case to work, the ace:checkboxButton needs to have it's value bound to a bean property and to have an <ace:ajax /> tag. Perhaps other components might need those two things to work as well.

I had modified the original test case to use ace:checkboxButton as well, and I spent some time testing the backport either without ajax or without having the value bound to a bean property, and it wasn't working as expected. The first issue was solved (checking the ace:checkboxButton was being done successfully and without selecting the row it was in), but an issue remained where after checking an ace:checkboxButton and then selecting the row, the checked state was lost. This scenario only works if the ace:checkboxButton is using <ace:ajax /> and its value is bound to a bean property.

Verified using attached test case and ICEfaces EE-3.3.0_P05 Jenkins build 2, Tomcat 8, MS Edge, IE 11, 10, 9, FF 53, Chrome 60.

When testing on IE 8 and 7, using Tomcat 8 or 7, the following console error was seen:
IE 8 - SCRIPT5007: Unable to get property 'instanceTag' of undefined or null reference
icepush.uncompressed.js (118,9). This issue is related to http://jira.icesoft.org/browse/ICE-11355. After removing the icepush-ee.jar the issue console error was no longer seen in IE 7 and 8.

That seems to be the same issue as http://jira.icesoft.org/browse/ICE-11355.

It doesn't happen when icepush.jar is not present.