IE 6.0 vs IE 5.0 top.window.name issue

[er441298]

we are upgrading an application which is JS heavy to run on IE6. When
in IE 5.0, and when the following command is executed on a child
window (top.window.name), it returns an actual window ID ( a number),
however the same comand executed in IE 6 returns a window name (ie.,
"mywind").

Our problem is that we have some other script which relays on the
window ID in order to read the attributes associated with with parent
screen in order to continue processing.

So we do not know how to get the actual window ID in IE 6, or some
other workaround. Please let us know if you can help..thanks

 

[Grant Wagner]

we are upgrading an application which is JS heavy to run on IE6. When
in IE 5.0, and when the following command is executed on a child
window (top.window.name), it returns an actual window ID ( a number),
however the same comand executed in IE 6 returns a window name (ie.,
"mywind").

You aren't executing a command, you are using IE specific syntax to
access a property of the current global window object that has the name
contained within top.window.name. So if top.window.name contains
"myWindow", you are really attempting to retrieve: window['myWindow'] or
window.myWindow.

So we do not know how to get the actual window ID in IE 6, or some
other workaround. Please let us know if you can help..thanks

Windows don't have ids. A window has a name, and a "handle" which is a
reference to the Window object pointing to the window.

 

[er441298]

thank you very much Grant. Yes we are using some JS script to running
on the client side IE browser. I may not have used the correct choice
of words, but what is very strange is this:

in IE 5.0 the following commad alert(top.window.name) returns a
number (handle)
in IE 6.0 the same command returns the actual wondow name

our application needs the window "handle" vs. the name in order for it
to process to the nest screen. Using JS, is there a way in IE 6 to
explicity call for the window handle vs. the name

THANK YOU SO MUCH