Tabset common problem fixed related to facet close.

command: Commit
Modified: D:\work\development\head\svn\ossrepo\icefaces2\trunk\icefaces\ace\component\src\org\icefaces\component\tab\TabSetRenderer.java
Sending content: D:\work\development\head\svn\ossrepo\icefaces2\trunk\icefaces\ace\component\src\org\icefaces\component\tab\TabSetRenderer.java
Completed: At revision: 22986

It came across that the issue is with the singleSubmit component. This component takes different path under IE8. Please see the attached snapshot of singleSubmit related js.

We do submit on "change" and "blur" event with all browsers and under IE we call submit on "focusout"event. So that is why under IE we don't see any change on checkbox selection until we tab out. So the fix needs to go in singleSubmit JS. I tried to use some other techniques, but under IE I am getting "event bubbling" behavior not "event capturing".

By looking at the code, I assume that we want to use event CAPTURING not event BUBBLING:
http://www.quirksmode.org/js/events_order.html

In past I have noticed there were some utility js, which normalizes this call for all browsers. Mircea might know about it.

On 07/11/10 6:08 PM, Ted Goddard wrote:

singleSubmit uses bubbling for efficiency – otherwise we would need to add
markup throughout the entire form. Unfortunately, I believe that "blur"
does not bubble on IE.

Ted.

On 08/11/10 9:14 AM, Mircea Toma wrote:

See this document:
http://www.quirksmode.org/blog/archives/2008/04/delegating%5Fthe.html .

It seems that onfocusin and onfocusout could be used.

Assign to Mircea to complete as this is related to ice:singleSubmit functionality.

'onchange' event cannot be used effectively in IE because the event is fired only when the modified element loses the focus. See http://msdn.microsoft.com/en-us/library/ms536912(VS.85).aspx . So, even if the event would propagate (bubble or capture) it still won't be fired as in the other browsers.

This document http://www.quirksmode.org/blog/archives/2008/04/delegating_the.html explains why you need to register the event handlers for 'onblur' and 'onfocus' for the capturing phase, it is only during this phase these events propagate through the DOM tree. So, the current code is correct since is registering the event handlers (onblur and onfocus) for the capturing phase.

Close this as "Won't fix" since there is no viable solution for fixing the 'onchange' behavior in IE. Also the current code is correct in using capturing phase for 'onblur' and 'onfocus'.