A fix for a previous regression may have resolved this issue as I was not able to replicate the problem. I the action and listener are both fired when clicking on a row.

Re-opening because the problem does manifest on IE but some caching can lead to misleading results (ie the page will work if you previously ran a working version and then re-deployed a non-working version). So once I cleared the cache between each redeployment, I could see the issue reliably.

This behaviour is a result of the compat resync work in http://jira.icefaces.org/browse/ICE-5252). IE works fine in rev 22018 but fails in 22019 which is the checking for the noted case.

I did a diff of the rendered source in the browser between the two revisions and discovered to notable differences:

Difference #1, there is an extra semicolon at the very end of the non-working source:

r22019
<tr class="iceDatTblRow1 iceRowSel" id="iceForm:dataTbl:0" onclick="Ice.registerClick(this,'iceForm:dataTblclick_row','iceForm:dataTblclick_count','0','iceForm',200,true,event,false,'iceForm:dataTblsel_rows','');" ondblclick="Ice.registerDblClick(this);" onmousedown="return Ice.preventTextSelection(event);" onmouseout="Ice.enableTxtSelection(document.body); this.className='iceDatTblRow1 iceRowSel'" onmouseover="this.className=' iceRowSelMouseOver';">

vs

r22018
<tr class="iceDatTblRow1 iceRowSel" id="iceForm:dataTbl:0" onclick="Ice.registerClick(this,'iceForm:dataTblclick_row','iceForm:dataTblclick_count','0','iceForm',200,true,event,false,'iceForm:dataTblsel_rows','');" ondblclick="Ice.registerDblClick(this);" onmousedown="return Ice.preventTextSelection(event);" onmouseout="Ice.enableTxtSelection(document.body); this.className='iceDatTblRow1 iceRowSel'" onmouseover="this.className=' iceRowSelMouseOver'">

Difference #2, there is an extra anchor rendered out in the non-working source that is not in the working source. It occurs in the first cell/column of each row only.

r22019 only
<a class="iceHdnLnk" href="#" id="iceForm:dataTbl_idx_0" onblur="return Ice.tblRowBlur(this);" onfocus="return Ice.tblRowFocus(this, false);">
<img src="/ICE-4288/xmlhttp/css/xp/css-images/spacer.gif" />
</a>

I've narrowed this down a bit more once I got the JavaScript debugging working in IE8.

The re-sync of the compat components was not done 100% due to the complexity of the some of the changes. So some component changes and some bridge changes were not applied. The problem I am seeing is related to event.js in that when the mouse is clicked on a row, the event is being detected in the following method as a NetscapeMouseEvent rather than an IEMouseEvent:

function $event(e, element) {
var capturedEvent = window.event || e;
if (capturedEvent && capturedEvent.type) {
var eventType = 'on' + capturedEvent.type;
if (contains(KeyListenerNames, eventType))

else if (contains(MouseListenerNames, eventType))

else

} else

}

In checking the 1.8 trunk, I noticed there is a fair amount of difference in the event adapting code compared to the 2.0 library. So it's likely that, due to the incomplete porting, there is some behavioural difference in what is being passed in or how the event is detected.

So just double checking with the debugger shows that the window.event is not set which causes the check to fall back to an NetscapeMouseEvent which in turn short circuits the rest of the submission.

I think I've exhausted what I can do here so have assigned to Mircea. Hopefully it's relatively easy to repair/update the changes from the re-sync of the compat components. IE is also showing a problem in Component Showcase where the collapsible panels aren't working but I think it is likely related to this issue as well.

The JIRA for the collapsible panel is: http://jira.icefaces.org/browse/ICE-5949

It seems that the table component Javascript is capturing the 'onclick' event and invokes iceSubmitPartial() function on a separate thread (using a setTimeout). This confuses the browser detection used for wrapping the original event into an IEEvent or NetscapeEvent type because 'window.event' global variable is not set by the browser anymore at the time the setTimeout executes.
Since window.event is missing the detection code falsely assumes that the browser is not IE and it can decorate the event with the NetscapeEvent object type.

The fix changes the event detection by testing for event properties that exist only in IE and also for properties that should not exist if the browser is IE.

Tested successfully on Icefaces2 revision# 22099
Passed in nightly regression test.