There is a bug with RadAjax Prometheus in that it is erroneously creating new <link> elements on an ajax response. (in IE7 if any client javascript code then loops through the stylesheets the poorly formed css HREF's result in "Access denied" errors, which is how I stumbled upon this)
You can verify this by creating a simple .aspx page, putting a button, a hidden field and a prometheus RadAjaxManager on the page. Have the button update the hidden field via RadAjaxManager. Start the page and use Fiddler (http://www.fiddlertool.com/fiddler/) or another HTTP debugger to watch the requests. Click the button. On the reponse, new <link> elements will be created with bad hrefs that generate HTTP 404 responses from the web server.
A brief technical description:
RadManager renders something similar to the following at the end of its AJAX reponse:
Sys.Application.add_init(function() {
$create(Telerik.Web.UI.RadAjaxManager,
{"ajaxSettings":[{InitControlID : "Button1",UpdatedControls
: [{ControlID:"HiddenField1",PanelID:""}]}],"clientEvents":{OnRequestStart:"",OnResponseEnd:""},"defaultLoadingPanelID":"","enableAJAX":true,"enableHistory":false,"links":[],"styles":[],"uniqueID":"RadAjaxManager1"},
null, null, $get("RadAjaxManager1"));
In it's WebResource.axd javascript, RadAjaxManager does this,
var _b=_a.substr(_a.indexOf("\"Links\":")+10,_a.indexOf("]",_a.indexOf("\"Links\":"))-(_a.indexOf("\"Links\":")+10)).replace(/\"/g,"");
Note the capital L in "Links", indexOf will return -1 since there is no match. And then adds 10 to this to start the substring. The script then goes on to split the resulting string on commas. This yields an array of strings like"cation.add_init(function() { $create(Telerik.Web.UI.RadAjaxManager"
"
{ajaxSettings:[{InitControlID : Button1"
"UpdatedControls :
[{ControlID:HiddenField1"
"PanelID:}"