It would be very good. Other components libraries (like Richfaces) do it.
In my company, we have many applications deployed on internet with Icefaces, and the constant call using AJAX sometimes make the user annoyed.

I think that this component is very important. Ajax is much better than general server submit if it needs server invoking, but client call is much better than Ajax if it doesn't need server invoking. Our customer asked us to replace ice:selectInputDate with a client date calendar (like myfaces' calendar), since the Ajax selecting a date is not convenient than a simple client calendar, same as the ice:panelCollapible. Thank you very much for considering this component.

Feature Request: Add client side handling of tree nodes on the ice:tree component. Specifically allow only one node to be open at a time.

It must be solved, because for minor event handling, Server-side round-trip is not viable,
Right now Icefaces's components goes to server (by Ajax) each time for event handling,
It is also possible to handle it on client-side by JavaScript!!!!!!

Hope, it will solved in next Release.

Just wanted to pitch in and say that the lack of this feature, ant the fact that this request was filed almost two years ago made me seriously reconsider the use of ICEFaces. If you're not close to the server hosting the components, the response time is killing the calendar for no good reason.

2009 -> wait 2sec -> 2008 -> wait 2sec -> 2007 -> wait 2sec .....

A client-only option should obviously be implemented as an alternative, if not as the default behaviour.

Client-side behaviors are coming along with the new ICEfaces 2.0 Component Suite. The initial pre-release will include a new datePicker, inputFile, slider, and tabset component. Many more components will be added after that.