Reference Rules and IE

[Brett Foster]

Ok this is driving me freekin nuts. I have a fairly simple class that
wraps mozilla XMLHttpRequest and Microsoft.XMLHTTP into a simple class.
It has worked but I've been caught by some sort of gotcha:

{
....
this.document = __global = new ActiveXObject("Microsoft.XMLHTTP");
....
}

when I press a button alert( that.document ) shows a dialog with an
empty string (i.e. not undefined, or null) and __global shows up as an
object. In Mozilla the expected behaviour is shown.

So what are the god damn rules for avoiding what ever the hell this
problem is?

Brett

[Martin Honnen]

Brett Foster wrote:

I have a fairly simple class that
wraps mozilla XMLHttpRequest and Microsoft.XMLHTTP into a simple class.
It has worked but I've been caught by some sort of gotcha:

{
...
this.document = __global = new ActiveXObject("Microsoft.XMLHTTP");
...
}

when I press a button alert( that.document ) shows a dialog with an
empty string (i.e. not undefined, or null) and __global shows up as an
object. In Mozilla the expected behaviour is shown.

The above line would yield an error in Mozilla. Make a minimal example
demonstrating the problem and post the full code or a URL to it.

--

Martin Honnen
http://JavaScript.FAQTs.com/

[Brett Foster]

Martin Honnen wrote:

Brett Foster wrote:

I have a fairly simple class that wraps mozilla XMLHttpRequest and
Microsoft.XMLHTTP into a simple class. It has worked but I've been
caught by some sort of gotcha:

{
...
this.document = __global = new ActiveXObject("Microsoft.XMLHTTP");
...
}

when I press a button alert( that.document ) shows a dialog with an
empty string (i.e. not undefined, or null) and __global shows up as an
object. In Mozilla the expected behaviour is shown.

The above line would yield an error in Mozilla. Make a minimal example
demonstrating the problem and post the full code or a URL to it.

Thanks, but the problem was that I was concatenating an object in to a
string and IE made it ''... It worked fine when by itself in the alert.
This was compounded by an insane webserver that was serving up strange
responses. Switched to apache2, and all was nice.

Thanks

Brett