David Golightly said the following on 8/30/2007 2:13 PM:
<snip>
> Whichever way you slice it, same result. How 'bout that: IE's
> equality operator is apparently broken.
It isn't IE's equality operator, it is IE's resolution of the window
object. If it were the equality operator then the the alerts would be
the same for window==g and g==window and they aren't. That alone says it
isn't the operator but something else.
Why anybody would need to compare a variable to window eludes me though.

Signature
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
dhtmlkitchen@gmail.com - 31 Aug 2007 05:20 GMT
> David Golightly said the following on 8/30/2007 2:13 PM:
>
[quoted text clipped - 7 lines]
> the same for window==g and g==window and they aren't. That alone says it
> isn't the operator but something else.
More on IE and window.event, see Dean's comment on window being not
equal to window.
http://www.davidflanagan.com/blog/2007_03.html
Interesting post on attachEvent's event argument.
http://www.davidflanagan.com/blog/2006_10.html#000114
> Why anybody would need to compare a variable to window eludes me though.
IF you have a popup or iframe.
var win = iframe.contentWindow;
window is weird in IE.
Garrett
> --
> Randy
> Chance Favors The Prepared Mind
> comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
> Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/