Attached test case that shows the issue.

Steps:

• Load welcomeICEfaces.jsf
• Click the 'Selection Changed' button.
• Try to navigate to another tab.
• The tabs content changes and the tabs are disabled but 'Tab One' is still shown as being selected.
• Click on the 'Enable Tabs' button. The tabs are now enabled. Clicking on another tab will show it as being active as well as the first tab.
• The tab set only becomes in sync when the first tab is selected again.

From my testing, using the tabSetProxy in another form, or without it and everything in one form, made no difference. The issue is that the javascript code that sets the tabPane(s) disabled runs before the code that finishes setting the selected tab index, and YUI tabview code won't set a tabPane selection on something that's disabled. So I deferred the setting of disabled=true.

icefaces3 trunk
Subversion 33800

Wanted to solve another one on the list of corner cases with disabled and tab changing. Found this while testing for this jira. I reworked the original fix for this jira to hopefully accommodate many more scenarios.

1. Deploy the Sparkle/Nightly/tabSet qa test app
2. Browse to: http://localhost:8080/tabSet/tabAttribute.jsf
3. Fill in the text field so it won't be an issue
4. Change the tabs around to ensure that works, then go to the first tab
5. Check the disabled checkbox, which will only make the first tab, that's currently selected, disabled
6. Click to change tabs to another one
7. When the code had the bug, the tab contents would change to the second tab's but the first clickable tab would remain blue. With the fix, the first tab does not remain blue, and only the clicked to tab is blue.

icefaces3 trunk
Subversion 33839