I have created a ticket for this as well, but I thought I would submit here as well and see if anyone has seen this behavior.
I am having an issue with the RadGrid and partial postbacks. For the partial postbacks I am using the RadScriptManager, RadAjaxManager, and the RadAjaxLoadingPanel.
The scenario is pretty basic. I click a button, some data is retrieved, and bound to the grid. The issue that is happening is the data retrieval process is pretty lengthy (upwards of 15-30 seconds). When the partial postback returns the grid has all of the data, but the styling for filtering, sorting, etc is all messed up.
A couple troubleshooting steps I have taken is to hard code the data being returned so it is faster. That actually fixes the problem and the grid comes back styled perfectly, so I am thinking it has to be the time to return is causing issues. I did find another person on the forum who described possibly a similar problem, and the recommendation was to increase the ScriptManager.AsyncPostBackTimeout value, which I have done, and that did not help.
Any assistance would be greatly appreciated. I am under the gun to get this done asap! Thanks
1 Answer, 1 is accepted
0
Hello Brad,
Opening a support ticket and a forum thread about the same thing is generally not recommended, but if you do so, please notify about this in both places.
Here is my answer from the support ticket:
I can suggest you a couple of things to check for a better understanding of the problem:
1. Are the CSS files returned by the web server in the AJAX request? If not, you may need to increase the timeout threshold even more. Is there a specific amount of time, after which the styles are not applied? You can sleep the thread during AJAX request to discover that more easily.
2. Is the problem observed only in Internet Explorer or in all browsers? IE has a limitation of 31 CSS files and <style> tags and cannot handle more. In this case it is good to combine non-embedded CSS files to reduce their number and use RadStyleSheetManager to combine the embedded CSS files.
If you are not adding RadControls to the page as a result of the AJAX request (i.e. all skins which will be used after the AJAX request are already present on the page beforehand), then you can set EnablePageHeadUpdate="false" to the RadAjaxManager.
Let us know how it goes. If the above information does not turn out to be helpful in tracking down the problem, please send us a simple runnable demo, which replicates the issue, so that we can investigate further. Thank you.
Greetings,
Dimo
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Opening a support ticket and a forum thread about the same thing is generally not recommended, but if you do so, please notify about this in both places.
Here is my answer from the support ticket:
I can suggest you a couple of things to check for a better understanding of the problem:
1. Are the CSS files returned by the web server in the AJAX request? If not, you may need to increase the timeout threshold even more. Is there a specific amount of time, after which the styles are not applied? You can sleep the thread during AJAX request to discover that more easily.
2. Is the problem observed only in Internet Explorer or in all browsers? IE has a limitation of 31 CSS files and <style> tags and cannot handle more. In this case it is good to combine non-embedded CSS files to reduce their number and use RadStyleSheetManager to combine the embedded CSS files.
If you are not adding RadControls to the page as a result of the AJAX request (i.e. all skins which will be used after the AJAX request are already present on the page beforehand), then you can set EnablePageHeadUpdate="false" to the RadAjaxManager.
Let us know how it goes. If the above information does not turn out to be helpful in tracking down the problem, please send us a simple runnable demo, which replicates the issue, so that we can investigate further. Thank you.
Greetings,
Dimo
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.