+ Start a Discussion
Gino BassoGino Basso 

Nested actionStatus components not allowed?

I have a VF edit page where changing one input value affects another (e.g. region and city select lists where selecting the regions filters the selectable list of cities). This was accomplished with actionSupport components as shown:

 

<!-- region --> <apex:pageBlockSectionItem > <apex:outputLabel for="regionSelectList" value="{!$ObjectType.Gem_Event__c.Fields.Region__c.Label}"/> <apex:outputPanel id="regionPanel" layout="none"> <apex:actionStatus id="regionStatus"> <apex:facet name="start"> <img src="{!$Resource.ActionStatusLoading}"/> </apex:facet> <apex:facet name="stop"> <apex:selectList id="regionSelectList" value="{!region}" size="1"> <apex:selectOptions value="{!regionOptions}"/> <apex:actionSupport event="onchange" rerender="cityPanel,formMessages" status="cityStatus" action="{!clearCity}"/> </apex:selectList> </apex:facet> </apex:actionStatus> </apex:outputPanel> </apex:pageBlockSectionItem> <!-- city --> <apex:pageBlockSectionItem > <apex:outputLabel for="citySelectList" value="{!$ObjectType.Gem_Event__c.Fields.Gem_City__c.Label}"/> <apex:outputPanel id="cityPanel" layout="none"> <apex:actionStatus id="cityStatus"> <apex:facet name="start"> <img src="{!$Resource.ActionStatusLoading}"/> </apex:facet> <apex:facet name="stop"> <apex:selectList id="citySelectList" value="{!Gem_Event__c.Gem_City__c}" size="1"> <apex:selectOptions value="{!cityOptions}"/> <apex:actionSupport rendered="{!ISNULL(region)}" event="onchange" rerender="cityPanel,regionPanel,formMessages" status="regionStatus"/> </apex:selectList> </apex:facet> </apex:actionStatus> </apex:outputPanel> </apex:pageBlockSectionItem>

 

 

Then I had need to rerender the entire section when another input field was changed, so I wrapped the entire page block section inside an actionStatus component. Only when I did all this all the start facets of the inner actionStatus components stopped working (the re-rendering continued to work however).

 

Eventually I had to abandon wrapping the entire section within an actionStatus component.

 

Is there a restriction on having nested actionStatus components?