ASP.NET AJAX UI

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

mattgi — Wed, 20 Sep 2006 05:05:53 GMT

Thanks Steve. I expect this fix to be in our next release.

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

TorgerJW — Thu, 31 Aug 2006 20:18:22 GMT

Bump. Me too.

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

MTri — Mon, 28 Aug 2006 15:32:32 GMT

This is an issue for me as well.

-MT

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

psyvision — Thu, 24 Aug 2006 14:03:17 GMT

I too am having this issue, except on an ajax heavy page.

I have a grid view on the right, an accordion on the left along with a popup control extender, update panels and an update progress.

The only thing that isn't working is the popup control extender which was diagnosed as having the same issue as Steve by using the Firebug extension for Firefox.

I am also using the July CTP with Firefox 1.5.0.6

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

StuWhite — Fri, 11 Aug 2006 11:18:56 GMT

I would have thought that quite a large number of Firefox users install extensions. I use the SearchStatus extension which causes the same problem.

I see this as a very serious bug and hope that the Atlas Development team can get it fixed quickly. I can't help but think that if the bug affected all IE users who had add-ons installed, then perhaps Microsoft would give it a higher priority...

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

steve harman — Mon, 07 Aug 2006 03:02:51 GMT

FYI - This thread didn't seem to be getting any attention, so I wrote up a post about the issue on my blog. If you are reading this tread and looking for more info, you might want to take a look at my post... and feel free to leave any feedback that you may have.

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

jeffreymcmanus — Mon, 07 Aug 2006 02:50:28 GMT

Atlas team, it would be terrific to get a workaround or a fix for this...I'm launching a site that uses Atlas soon and I might have to scale back my use of Atlas because of this problem.

Re: Browser Plugins Cause javaScript Exception in Async Callback Handler...

steve harman — Wed, 02 Aug 2006 12:41:17 GMT

Looks like the link to my old post about the exception didn't work... so try this one.

Browser Plugins Cause javaScript Exception in Async Callback Handler...

steve harman — Wed, 02 Aug 2006 02:32:15 GMT

I posted about this issue before, but didn't root-cause it as I *thought* a fix was on the way in the July CTP. I was wrong.

If you read the post I linked to above, you will see a snippet of the following method (from the Atlas.js file):

this._updateStyleSheet = function(cssText)
{
var head = document.getElementsByTagName('HEAD')[0];
var styles = document.styleSheets;
var styleSheet = styles[styles.length - 1];

if (Sys.Runtime.get_hostType() == Sys.HostType.InternetExplorer)
{
    styleSheet.cssText = cssText;
}
else
{
    for (var i = styleSheet.cssRules.length - 1; i >= 0; i--)
    {
      styleSheet.deleteRule(i);
    }
var ruleLines =cssText.split('}');
for (var j =0;j <ruleLines.length;j++)
{
var rule =ruleLines[j];
var index =rule.indexOf('{');
var style =rule.substr(index +1).trim();
if (style.length !=0)
{
var selector =rule.substring(0,index).trim();
styleSheet.insertRule(selector +'{'+style +'}', styleSheet.cssRules.length);
}
    }
  }
}

The line in red is the root cause of the issue, and the symptom (a NS_ERROR_DOM_BAD_URI exception) is caused by the line in blue.

Now, here's the issue... some Firefox plugins (i.e. - the CoComment Extension) will load an external stylesheet after the page has been downloaded, putting the plugin's stylesheet at the end of the document.styleSheets array.

This is a problem as the _updateStyleSheet method expects the last item of the array to be some stylesheet specific to the Atlas framework. But due to the plugin, it isn't at the end (at index styles.length-1), but rather it is two from the end (at index styles.length-2).

With the CoComment plugin this causes an issue because we don't seem to have access to the URI, and styleSheet.cssRules will throw the mentioned exception. I would suggest that instead of blindly assuming the Atlas specific styleSheet is at the end of the array, the _updateStyleSheet method should go thru the array (from end to start) looking for a specific attribute of the <script> tag ... or better yet, the ID!

This should be considered a big issue as I'm sure there are plenty of other plugins/extensions for Firefox (and likely other browsers) that will cause the same issue.

Also... is this the right place to report such bugs, or is there a bug-tracker that the Atlas team uses and /or I can contact them directly?

Thanks in advance!