The strange behavior of borderPanel is due to the fact that the backing bean is in request scope and uses ValueChangeListener to update. In request scope, the bean has default values for each request, so only sees the correct value for the one checkbox that is selected. The solution is to either use values directly or to use beans in view scope.

ice:loadBundle was not working correctly during the decode phase. Rather than attempt to repair ice:loadBundle, it probably makes more sense to recommend that people switch to f:loadBundle.

> Mircea, please comment on why focus appears to be lost with the selectMany components. Is it a difference in behavior
> between the JSF 2.0 JavaScript DOM manipulation and ICEfaces DOM manipulation?

There are two things that are different:
a) There is no update for the 'select' element that triggered the submit. We have BridgeFacesContext.applyBrowserChanges() method that applies the changes from the browser to the old DOM thus canceling useless updates.
b) selectOne and selectMany components are sending an additional focus command that helps maintaining focus on the submit triggering element.

Apply input values to old DOM to avoid generating pointless updates. As side effect the focus is preserved on the submit triggering element.

Excellent; this fix was also needed to clear the input field in the chat portion of the auction demo.

Focus is working well in component-showcase now, however, the chat field mentioned above loses focus (I will add this investigation to an auction-specific bug).