Greetings:
I am using the latest Rad Controls for ASP.Net for AJAX (2008.2 1001).
I have a radtabstrip that on the server side makes visible a DIV based upon which one of 3 tab enties is pressed.
Using an RadAjaxManagerProxy (main manager is in master page), I add an AjaxSettings for the tabstrip to update the tabstrip itself plus all three of the potential DIVs that may be made visible.
Works great in IE.
In Netscape 7.2 it is as if the Ajax times out before the server can take action. The results are that the DIVs remain the same even though the server has changed their visual behavior.
If I step through the code in debug mode, it somehow works fine. (timing I guess). And it always works fine in IE.
If I remove the Ajaxification of the tabstrip it works fine in Netscape although the whole page refreshes.
I can find no references to anything on your site regarding Netscape and timing.
Any ideas why Netscape would have an Ajax timing problem ?
Any way I can disable Ajaxification of the tabstrip if the client is Netscape ?
All ideas welcome and appreciated.
The five most common words in a web developer's vocabulary are ..."It-Doesn't-Work-In-Netscape" <g>.
Thanks,
Robb
I am using the latest Rad Controls for ASP.Net for AJAX (2008.2 1001).
I have a radtabstrip that on the server side makes visible a DIV based upon which one of 3 tab enties is pressed.
Using an RadAjaxManagerProxy (main manager is in master page), I add an AjaxSettings for the tabstrip to update the tabstrip itself plus all three of the potential DIVs that may be made visible.
Works great in IE.
In Netscape 7.2 it is as if the Ajax times out before the server can take action. The results are that the DIVs remain the same even though the server has changed their visual behavior.
If I step through the code in debug mode, it somehow works fine. (timing I guess). And it always works fine in IE.
If I remove the Ajaxification of the tabstrip it works fine in Netscape although the whole page refreshes.
I can find no references to anything on your site regarding Netscape and timing.
Any ideas why Netscape would have an Ajax timing problem ?
Any way I can disable Ajaxification of the tabstrip if the client is Netscape ?
All ideas welcome and appreciated.
The five most common words in a web developer's vocabulary are ..."It-Doesn't-Work-In-Netscape" <g>.
Thanks,
Robb