Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.2, EE-3.2.0.GA
-
Fix Version/s: 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Salesforce Case Reference:
Description
If the tabs in the ace:tabSet are set to be disabled and this code is done in the tabChangeListener, the content of the tab is changed but the 'active' tab is kept to the previously selected tab. This causes the tabSet to become out of sync, with the active tab and content showing different contents.
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