Question

In IE.

window === top; // false
window === window.window // false
window == top; // true
window == window.window // true

In FF3.6 & Chrome stable this doesn’t happen.

In IE typeof, .toString, Object.prototype.toString.call all return the same for both top & window

This is related to this.

Can anyone tell me why IE can’t do strict equivelance?

Note that circular reference doesn’t cause issues in both IE & Chrome.

o = {};
o.o = o;
o === o.o; // true

Turns out

window.window === window.top; // true
window.window === window.self; // true

So it’s an issue with getting window on it’s own.

for (var i in window) {
    if (window.window[i] !== window[i]) {
        console.log(i); // external, frames, clipboardData
    }
}

[Edit]

This is just getting stupid now:

 window.frames === window.frames; // false
 window.frames == window.frames; // false
 window.external == window.external; // true
 window.external === window.external; // false
 window.clipboardData === window.clipboardData; // false
 window.clipboardData == window.clipboardData; // false

[Further edit]

turns out that window.frames holds a pointer to the ie debugger. So having the debugger open changes the window object. I have to do some more testing.

window.frames.location === window.frames.location; // false
window.frames.location == window.frames.location; // true
window.frames.event.boundElements == window.frames.event.boundElements; // false

Not to mention that window.external just does not play nicely

>>for (var i in window.external) alert(i);
"Object doesn't support this action"

Answer 1

This isn’t exactly a bug: host objects can do whatever they like, and the window object is a particularly complicated beast, serving the dual purposes of being the object that represents the browser window and also being an alias for the global object. I’d chalk this one up as a weirdness and avoid using the strict === operator when comparing Window objects.

Note that this isn’t a “JavaScript is weird” shrugpost. As well as serving as the global object, window is a host object and pre-HTML5 could legitimately (according to spec, at least) behave however it liked. Older versions of IE take advantage of this freedom and exhibit much quirky behaviour for which there is no specification whatsoever. Trying to understand it all without access to the source code is a pointless exercise.