Re: ajax error on firefox

so ... what .. is this a dirty little secret that I wasn't supposed to
mention ?

Is no one else using asp.net ajax web service calls or are they just
ignoring any browsers that generate this error ?


"germ" <germ@xxxxxxxxxx> wrote in message
news:u3L2cdcuHHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
doing a simple page webmethod call an a page via PageMethods works fine in
ie7 & opera9
the same call on firefox ( and I assume netscape ) generates the following
error :

Error: [Exception... "Component returned failure code: 0x80040111
(NS_ERROR_NOT_AVAILABLE) [nsIXMLHttpRequest.status]" nsresult:
"0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame ::
http://hgha.gerzio.ca/ScriptResource.axd?d=3Ot8FdrYMQ58gwjNF6tbd8V5YtBKDtb8a6qI5cjRJWaZBQhYu2jjDRnc7N0IverhgY8x7LACpAIvqLPvNyERF0ui1Tz1p-s2eu0h41S_qMA1&t=633179517344763787
:: Sys$Net$XMLHttpExecutor$get_statusCode :: line 4166" data: no]
Source File:
http://hgha.gerzio.ca/ScriptResource.axd?d=3Ot8FdrYMQ58gwjNF6tbd8V5YtBKDtb8a6qI5cjRJWaZBQhYu2jjDRnc7N0IverhgY8x7LACpAIvqLPvNyERF0ui1Tz1p-s2eu0h41S_qMA1&t=633179517344763787
Line: 4166

The script code this points to is :
//-----------------------------------------------------------------------
// Copyright (C) Microsoft Corporation. All rights reserved.
//-----------------------------------------------------------------------
// MicrosoftAjax.js
// Microsoft AJAX Framework.

. . .
function Sys$Net$XMLHttpExecutor$get_statusCode() {
/// <value type="Number"></value>
if (arguments.length !== 0) throw Error.parameterCount();
if (!this._responseAvailable) {
throw
Error.invalidOperation(String.format(Sys.Res.cannotCallBeforeResponse,
'get_statusCode'));
}
if (!this._xmlHttpRequest) {
throw
Error.invalidOperation(String.format(Sys.Res.cannotCallOutsideHandler,
'get_statusCode'));
}

return this._xmlHttpRequest.status;
}


Google turns up a number of references to this problem in general but no
fixes for asp.net ajax in particular.
Since this problem is caused by a problem buried in the microsoft ajax
code I am at a loss as to how to proceed.
Do we just drop ajax for firefox & netscape users until MS puts out a fix
?
Or is there a fix out there that I haven't stumbled across yet ?
Gerry



.