Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.1.0.RC1, EE-3.0.0.GA_P01
-
Fix Version/s: 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces3/trunk # 29691
Passed at: ICEfaces3/trunk# 29188
Description
1. Build / deploy test app located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/tabSet
2. Navigate to '/dataStructures/tabRepeat2.jsf'
3. Click on one of the 'updatePushVal' buttons
4. First issue is seen, notice that the text values in the tabSets on the right have disappeared
5. Try and change to 'tab2' in one of the tabs on the left
6. Second issue is seen, the tab content is never displayed
Issue Links
- depends on
-
ICE-8747
FixViewState use of StateManager.getViewState(FC) disrupts state saving under MyFaces
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | REGRESSION: ACE:TabSet inside a ui:repeat - Unable to succesfully switch tabs after calling button actionListener | REGRESSION: ACE:TabSet inside a ui:repeat - Unable to switch tabs after calling button actionListener |
| Salesforce Case | [] | |
| Fix Version/s | 3.1 [ 10312 ] | |
| Assignee Priority | P2 | |
| Affects Version/s | 3.1.0.RC1 [ 10337 ] | |
| Assignee | Mircea Toma [ mircea.toma ] |
| Salesforce Case | [] | |
| Fix Version/s | 3.2 [ 10338 ] | |
| Fix Version/s | 3.1 [ 10312 ] |
Verified if this issue goes away when rolling back to a revision before the fixes for ICE-8278 (rev #29665). Unfortunately, it doesn't. Actually this issue does't seem to be in core. It looks like that during an update (triggered when one of the updatePushVal buttons is clicked) the tabSet state is not completely loaded, in the clientSide mode. In serverSide mode the tabs do not issue any postbacks, thus the tab switch does not occur.
| Salesforce Case | [] | |
| Assignee | Mircea Toma [ mircea.toma ] | Mark Collette [ mark.collette ] |
| Salesforce Case | [] | |
| Affects Version/s | EE-3.0.0.GA_P01 [ 10327 ] |
debug diffConfig shows that when the commandButton is clicked, the two components inside the ui:repeat, the tabSet on the left and the panelGroup on the right (which holds a tabSet), are both rendered using a clientId that omits the ui:repeat's iteration index. The tabSet's script tag's rendered id also omits the ui:repeat's iteration index, and the second tabPane in the tabSet seems to become unrendered. This might be somehow due to the UIInstructions components used for the table markup.
| Assignee Priority | P2 [ 10011 ] | P1 [ 10010 ] |
| Fix Version/s | 3.3 [ 10370 ] | |
| Fix Version/s | 3.2 [ 10338 ] |
| Assignee Priority | P1 [ 10010 ] |
Testing shows that the resolution of ICE-8747 fixed this.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
This seems to be related to the changes for
ICE-8278. Lower priority, can be looked at after P1 issues.