Sep 27, 2012, 2:08 PM
IE9 Blank Page after deployment
Hi,
In our previous Ext.NET 1.X version, when we run our application against IE9 and Login or Main pages are loaded, there were a lot of times where web page appears in blank, and a refresh was needed in order to load web page as required.
So in this way, we had this hack code just for IE9 browser to avois this problem:
Now, with Ext.NET 2.1 version, it looks that this hack is not working and we have the same problem just after a new deployment is performed.
At the moment, we can solve this issue just setting this code for all browsers:
If code is rendered in the same page and not as a separated javascript file, would we loose recource's cache capability of some browsers?
Thanks.
In our previous Ext.NET 1.X version, when we run our application against IE9 and Login or Main pages are loaded, there were a lot of times where web page appears in blank, and a refresh was needed in order to load web page as required.
So in this way, we had this hack code just for IE9 browser to avois this problem:
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
// HACK: Parche para pantalla en blanco en IE9
if (Request.Browser.Browser == "IE" && Request.Browser.MajorVersion == 9)
resManager.InitScriptMode = InitScriptMode.Inline;
}
</script>
<ext:ResourceManager ID="resManager" runat="server" ViewStateMode="Disabled" />
Now, with Ext.NET 2.1 version, it looks that this hack is not working and we have the same problem just after a new deployment is performed.
At the moment, we can solve this issue just setting this code for all browsers:
<ext:ResourceManager ID="resManager" runat="server" ViewStateMode="Disabled" InitScriptMode="Inline" />
But, is there any performance drawback using Inline mode for all browsers instead of Linked?If code is rendered in the same page and not as a separated javascript file, would we loose recource's cache capability of some browsers?
Thanks.