<xhtmlConformance mode="Legacy" />
in the system.web section of our web config file.
I was not able to get the AjaxPanel to work when this is on. Setting it to "transitional" or "strict" cause the panel to work nicely. Unfortunately, changing this seetting at this time is not a choice for us. Is the another way to make this work?
5 Answers, 1 is accepted
Could you please test the application by using regular asp UpdatePanel instead of RadAjaxPanel and let me know if it makes any difference. You could also review the following blog post for more information on this matter.
Sincerely yours,
Maria Ilieva
the Telerik team
I tested the problem by setting <xhtmlConformance mode="Legacy" /> in the web.config in the demo solution.
This fails the same way my application does.
Isn't that sufficient for you to determine if your ajaxpanel will work in legacy mode?
Are you saying that if I succeed in adding UpdatePanel to my app, then I do not need to use your ajaxpanel?
The results of usage of asp UpdatePanel will help us determine if this is generic ASP problem or is directly related with RadAjax. I suppose that the problem is general with the asp Ajax and as our controls are build on its top it will appear with RadAjax also.
Sincerely yours,
Maria Ilieva
the Telerik team
I also stated that this failure can be easily seen in your demo code.
Can't you try UpdatePanel and see the results?
if your stuff is built on UpdatePanel, then unlike me, you should be able to easily do this test.
After testing the mentioned setting with regular asp UpdatePanel the same problems are observed. It seems that the legacy mode is not fully compatible with ASP Ajax. Please review the following post for more information on this matter.
Sincerely yours,
Maria Ilieva
the Telerik team