I'm using ace:tabSet with clientSide="false" and all my tabPanes have cacheOnClient="true". The caching behavior is as expected and when a tab is selected, the cached dom node are show instantly and an ajax request updates the state of the tabs behind the scenes. The problem is that once this ajax request returns, the tab that originally fired gets selected even if the user had selected another one before the original ajax request is returned.

If the user is on tab A and clicks on tab B and immediately clicks on tab C, he will get to tab C but once the state has been updated on the server for the tab B click event, the user is brought back to tab B and after a the update for the tab C click event is done, is again brought back to tab C. Very confusing to the user.

To reproduce the problem use attached files to recreate a sample ICEfaces2.1BETA2 project. Once up and running click on tab B and then within 2 seconds click on tab C. Wait for a second or two.

The update of the tabset state on the server should not have any effect on the client side (it should not switch to a tab) since the client side already reflects the correct state. If this is not possible, we should have a way to tell the component not to change tab after the state is updated.