function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
saasdevsaasdev 

Rerender not working in some versions of IE6

Hi All

 

I have creaed a visual force page that rerenders some images depending on what value is selected in a picklist - this works fine in Firefix, IE7, and most instances of IE 6, however, one version of IE (Explorer 6.02.2900.2180.spsp_sp2_gdr.080814.1233 (Version update SP2)), it does not seem to work in (which is handily, the one everyone uses, but not the one I developed on). The action support for the change in the picklist reruns the apex behind the page to generate the new image, and also rerender the ouput panel the image resides in. What I'm wondering is whether in this instance of IE, the rerender is happening before the apex updates the image url, thus it is not showing. Is there any way I can get to the javascript that is being run on the rerender so I can include a wait() function?

 

Page Code:

 

<td style="border-style:solid;border-width:0 2px 2px 0;vertical-align:top;width:50%;">
<apex:form style="{vertical-align:top}">
<div style="margin-left:100px">Please Select Date :</div>
<br/>
<apex:selectList value="{!AgentSalesDate}" multiselect="false" size="1" style="margin-left:100px">
<apex:selectOptions value="{!AgentSalesDateList}"> </apex:selectOptions>
<apex:actionSupport event="onchange" action="{!AgentSalesChange}" rerender="AgentSales"></apex:actionSupport>
</apex:selectList>
<br/>
<apex:outputPanel id="AgentSales">
<br/>
<img src="{!imageurl}"/>
</apex:outputPanel>
</apex:form>
</td>

 

 

Controller Code:

 

//function reruns the MainPageController to recalculate the image url
public void AgentSalesChange() {
MainPageController2();
}//end function

 

 

 

Thanks

dchasmandchasman

First we've heard of something like this. Can you please post the code for the entire controller (e.g. want to see what you're doing in mainPageController2()). Even betterhave you repro'ed this with a simple isolated test case that you could post?

 

Rerender/partial page update does not update the underlying <img> element in the DOM in the way you might think it does - an entirely new <img> is sent to the browser and a container div's innerHTML is set... We have seen some odd behavior in IE6 around caching images and PDF's etc that we have worked around when needed by swizzling in a timestamp into generated URLs...