J. Moreno said the following on 7/28/2006 8:30 PM:
> This works under Win200 and 6.0.2800.1106.
>
> But not under WinXp and 6.0.2900.2180.
>
> Does anyone know what IE might be looking for?

Signature
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
> J. Moreno said the following on 7/28/2006 8:30 PM:
> > Hi,
[quoted text clipped - 5 lines]
>
> What does item(1) refer to?
An individual frame. In FF window.parent.frame[1] works.
> What is "position"?
An ID (yeah, I know, bad idea to have more than one element with the same
ID, I'll fix that next).
> > This works under Win200 and 6.0.2800.1106.
> >
[quoted text clipped - 3 lines]
>
> Not even MS is sure what IE might be looking for about 90% of the time.
Heh. But I need to find out what it wants this time...

Signature
J. Moreno
Randy Webb - 31 Jul 2006 19:30 GMT
J. Moreno said the following on 7/31/2006 12:08 PM:
>> J. Moreno said the following on 7/28/2006 8:30 PM:
>>> Hi,
[quoted text clipped - 6 lines]
>
> An individual frame. In FF window.parent.frame[1] works.
IE only code, gotta love it.
>> What is "position"?
>
> An ID (yeah, I know, bad idea to have more than one element with the same
> ID, I'll fix that next).
It's not just a "bad idea" as it is invalid HTML code and when presented
with invalid HTML anything goes.
>>> This works under Win200 and 6.0.2800.1106.
>>>
[quoted text clipped - 4 lines]
>
> Heh. But I need to find out what it wants this time...
Start with validating the HTML to make sure it isn't a multiple ID issue
as IE may make a collection of same-ID'ed elements (I don't remember to
be honest). Then, start debugging with alerts and find out what is
causing the error.

Signature
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/