StyleSheetManager Combine and AJAX

[MD]

I'm having an issue with the RadStylesheetManager not combining the css files on AJAX requests.  The RadStylesheetManager works properly on the intial page request, but on AJAX requests I see individual WebResource requests to WebResource.axd and not Telerik.Web.UI.WebResource.axd.  The RadScriptManager residing on the same page works as expected during AJAX requests combining the script files for the controls and using the Telerik handler.  I've tested this with both Fiddler and Firebug and tried this with both IE and FireFox using both Q3 2008 and the latest nightly build of Q2 2009.

Any help would be appreciated.

Thanks
Matt

[Atanas Korchev]

Hi MD,

This is the expected behavior. The calls to WebResource.axd are because of the images used in the skins. The stylesheetmanager combines the CSS files only. All images are served separately.

Regards,
Albert
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[MD]

Thanks for the reply, but I guess I wasn't clear enough.  There is only one call the Telerik.Web.UI.WebResource.axd on the AJAX call and that is for the javascript files from the RadScriptManager which is combining and compressing the javascript files; however, there is not a call to Telerik.Web.UI.WebResource.axd for the combined css files.  I understand the images are handled seperately through WebResource.axd since there is now way to combine them and it is unwise to have them compressed, but I am seeing numerous calls to WebResource.axd for each controls css files.  On the initial page visit the css files are combined and compressed and I see the single call to Telerik.Web.UI.WebResource.axd, but on the AJAX calls I am seeing calls to WebResource.axd for each individual css file for the RadControls.

Thanks
Matt

[T. Tsonev]

Hello,

We can confirm that the CSS files are served separately on AJAX update. This is a known limitation in RadScriptManager that we plan to fix. The only workaround for the moment is to set the EnableAjaxSkinRendering to "false". This is only applicable to controls that are initially visible on the page and not to those  rendered as a part of an AJAX update.

We apologize for the inconvenience.

All the best,
Tsvetomir Tsonev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[MD]

Just wanted to check and see if this will be included in the next version (Q3 this fall) or possibly in a newer build of Q2?  No rush, but I just wanted to know.

Thanks

[T. Tsonev]

Hello,

We'll try to fit it in the schedule, but it's not clear at the moment if we'll manage to. That will depend on how well we progress with the tasks for Q3 that we're already committed to. Please, excuse us for the inconvenience.

Sincerely yours,
Tsvetomir Tsonev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[MD]

Was this added with the Q3 release?

[T. Tsonev]

Hi,

No, the issue is still open for the moment. We have added this on the list of problems to fix for Q1, but we'll also include it in the internal builds / service packs for Q3 if we complete it sooner.

Greetings,
Tsvetomir Tsonev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.