ScriptResource.axd error in Firefox

[Simon]

Hi,

(Note: This thread was mistakenly posted in the "RadUpload" section; very sorry about that!)

We're getting a really odd error occur with an application using a range of Telerik controls (RadEditor, RadGrid, RadTreeView, etc) that works fine in IE7 but in Firefox we are seeing the following error appear in the Firefox Error Console when we load the first of several controls. Once the error has occurred, no script or styles appear to work in any subsequent controls.

This error fires once the first control has loaded, regardless of the type of control we have loaded first.

Error: uncaught exception: [Exception... "An invalid or illegal string was specified"  code: "12" nsresult: "0x8053000c (NS_ERROR_DOM_SYNTAX_ERR)"  location: "http://rexshad-74306jb/ExhibitorPortal/Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=RadScriptManager1_HiddenField&_TSM_CombinedScripts_=%3b%3bTelerik.Web.UI%2c+Version%3d2007.3.1425.35%2c+Culture%3dneutral%2c+PublicKeyToken%3d121fae78165ba3d4%3aen-US%3a48a19736-c022-4131-bf7d-fcbe4aa553d6%3a393f5085%3a34f9d57d%3a526d426%3a80c4ad6d%3a527acb41%3a3c2b629f%3acf187033%3a37e97092%3a1d42ade9%3a251a9451%3a81330300%3a9703c1f0%3aa3f85c94%3a665c7bcf Line: 1245"]
Source File: http://rexshad-74306jb/ExhibitorPortal/ScriptResource.axd?d=WGHC5g2LE5q9GhN0AU7_4qkFZDYtNUOA5TB5ypjC8hQ0d-S9H_HIVOVooM3ftG-Ld-aE8DJ11qSdAW3PEQKdI7qrAYqAZty6lLy15AUaGUA1&t=633386647776777396
Line: 4305

I know I need to put more info up here, but I just wanted to see if anyone had even seen this before?

It seems to me to be a problem with the request being sent to the ScriptResource.axd - possibly a character that isn't being escaped... although I may be completely wrong!

[Simon]

I've done a bit more digging and found the error is occurring on the first call that any RadControl makes to ScriptResource.axd.

The function it is failing on is below, the breakpoint marked in red. I really have no idea why this might only be happening in Firefox only...

4277 function Sys$_ScriptLoader$_loadScriptsInternal() {
4278 // Load up the next script in the list
4279 if (this._scriptsToLoad && this._scriptsToLoad.length > 0) {
4280 var nextScript = Array.dequeue(this._scriptsToLoad);
4281 // Inject a script element into the DOM
4282 var scriptElement = this._createScriptElement(nextScript);
4283
4284 if (scriptElement.text && Sys.Browser.agent === Sys.Browser.Safari) {
4285 // Safari requires the inline script to be in the innerHTML attribute
4286 scriptElement.innerHTML = scriptElement.text;
4287 delete scriptElement.text;
4288 }
4289
4290 // AtlasWhidbey 36149: If they queue an empty script block "", we can't tell the difference between
4291 // a script block queue entry and a src entry with just if(!element.text).
4292 // dont use scriptElement.src --> FF resolves that to the current directory, IE leaves it blank.
4293 // nextScript.src is always a string if it's a non block script.
4294 if (typeof(nextScript.src) === "string") {
4295 // We only need to worry about timing out and loading if the script tag has a 'src'.
4296 this._currentTask = new Sys._ScriptLoaderTask(scriptElement, this._scriptLoadedDelegate);
4297 // note: task is responsible for disposing of _itself_. This is necessary so that the ScriptLoader can continue
4298 // with script loading after a script notifies it has loaded. The task sticks around until the dom element finishes
4299 // completely, and disposes itself automatically.
4300 // note: its possible for notify to occur before this method even returns in IE! So it should remain the last possible statement.
4301 this._currentTask.execute();
4302 }
4303 else {
4304 // script is literal script, so just load the script by adding the new element to the DOM
4305 document.getElementsByTagName('HEAD')[0].appendChild(scriptElement);
4306
4307 // DevDiv 74151: Do not assume the script executes synchronously. Use a setTimeout to delay
4308 // proceeding, which ensures the script executes before we continue. This was first introduced
4309 // as a workaround for a Firefox bug, but we do it for all browsers in order to avoid making
4310 // an assumption that may be wrong in the future. Executing the script synchronously is not
4311 // in any spec or recommendation.
4312 var scriptLoader = this; // used in the setTimeout closure
4313 window.setTimeout(function() {
4314 // cleanup (removes the script element in release mode).
4315 Sys._ScriptLoader._clearScript(scriptElement);
4316 // Resume script loading progress.
4317 scriptLoader._loadScriptsInternal();
4318 }, 0);
4319 }
4320 }
4321 else {
4322 // When there are no more scripts to load, call the final event
4323 var callback = this._allScriptsLoadedCallback;
4324 this._stopLoading();
4325 if(callback) {
4326 callback(this);
4327 }
4328 }
4329 }

[Rosen]

Hello Simon,

Unfortunately I'm not sure what might be the cause of issue you are facing with the supplied details. Can you please send us (attached to a formal ticket) a small working project in which this behavior can be reproduced? Then will be able to further investigate this problem and hopefully find a suitable solution.

Greetings,
Rosen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Dave]

I'm encountering the same error on my page; the only Telerik control on the page is an Editor.

Did a fix come out of this issue at all?

Thanks,
Dave

[Rumen]

Hi Dave,

Could you please replace RadScriptManager with asp:ScriptManager and see whether the problem still persists?

If this does not solve the problem, please open a support ticket and send a sample running project that demonstrates the issue. We will examine the project and find the reason for the problem. After that we will try to provide a solution.


Best regards,
Rumen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Marty]

Could you please replace RadScriptManager with asp:ScriptManager and see whether the problem still persists?

I was having the same problem and did the above.  It solved it, but when will this bug be fixed?

[T. Tsonev]

Hello Marty,

I am glad this helped. Unfortunately, we still cannot reproduce the problem in our test environment. It will be of great help if you can send us the page you are working on. We also need the exact version of the Telerik.Web.UI assembly. Thank you.

Kind regards,
Tsvetomir Tsonev
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.