In FF1.5.0.1 I note an intermittent problem with javascript: TOP
sometimes becomes undefined.

top is a JavaScript global that represents the containing topmost window
(esp. useful from frames within a frameset). I have never seen it
undefined in either a fully or partially loaded page in any browser
since NS4.72 before.

Oddly, it is initially defined, but after clicking on links in the
frame, it becomes undefined.

The application JavaScript has been running ok since Netscape 4.72. :)

In more detail: I have a frameset, with four frames. Clicking on any of
a large number links in a frame, calls a javascript function which
either creates a new floating window, or updates the location of one of
the other frames, and returns false so that the link does not fire.

I can click on a links in the frame, and windows open or update
correctly, but after a few (5-8) clicks in the frame (that itself is NOT
changed), top becomes undefined.

We use FF in our Dev environment, so this is the first version of FF
where we have noted the problem - and yes, we were using the pre-release
betas as they became available.

I have been trying to construct a simple example that reliably
duplicates the problem, with no luck yet. Unfortunately, I have no
official remaining time budget for more investigation (three days so far
:() and we have had to move our dev environment to IE6.

Does anyone know of circumstances where FF JavaScript loses top?

Regards & thanks,
Jeff

Jeff wrote:
> In FF1.5.0.1 I note an intermittent problem with javascript: TOP
> sometimes becomes undefined.
>
> top is a JavaScript global that represents the containing topmost window
> (esp. useful from frames within a frameset). I have never seen it
> undefined in either a fully or partially loaded page in any browser
> since NS4.72 before.
>
> Oddly, it is initially defined, but after clicking on links in the
> frame, it becomes undefined.
>
> The application JavaScript has been running ok since Netscape 4.72. :)
>
> In more detail: I have a frameset, with four frames. Clicking on any of
> a large number links in a frame, calls a javascript function which
> either creates a new floating window, or updates the location of one of
> the other frames, and returns false so that the link does not fire.
>
> I can click on a links in the frame, and windows open or update
> correctly, but after a few (5-8) clicks in the frame (that itself is NOT
> changed), top becomes undefined.
>
> We use FF in our Dev environment, so this is the first version of FF
> where we have noted the problem - and yes, we were using the pre-release
> betas as they became available.
>
> I have been trying to construct a simple example that reliably
> duplicates the problem, with no luck yet. Unfortunately, I have no
> official remaining time budget for more investigation (three days so far
> :() and we have had to move our dev environment to IE6.
>
> Does anyone know of circumstances where FF JavaScript loses top?
>
> Regards & thanks,
> Jeff

My suggestion is to try this newsgroup:
mozilla.dev.tech.js-engine
on this server.

--
Gus

T-bird Leader Jeff radioed the tower , on 2/17/2006 3:59 AM:

> In FF1.5.0.1 I note an intermittent problem with javascript: TOP
> sometimes becomes undefined.
>
> top is a JavaScript global that represents the containing topmost window
> (esp. useful from frames within a frameset). I have never seen it
> undefined in either a fully or partially loaded page in any browser
> since NS4.72 before.
>
> Oddly, it is initially defined, but after clicking on links in the
> frame, it becomes undefined.
>
> The application JavaScript has been running ok since Netscape 4.72. :)
>
> In more detail: I have a frameset, with four frames. Clicking on any of
> a large number links in a frame, calls a javascript function which
> either creates a new floating window, or updates the location of one of
> the other frames, and returns false so that the link does not fire.
>
> I can click on a links in the frame, and windows open or update
> correctly, but after a few (5-8) clicks in the frame (that itself is NOT
> changed), top becomes undefined.
>
> We use FF in our Dev environment, so this is the first version of FF
> where we have noted the problem - and yes, we were using the pre-release
> betas as they became available.
>
> I have been trying to construct a simple example that reliably
> duplicates the problem, with no luck yet. Unfortunately, I have no
> official remaining time budget for more investigation (three days so far
> :() and we have had to move our dev environment to IE6.
>
> Does anyone know of circumstances where FF JavaScript loses top?
>
> Regards & thanks,
> Jeff

Interesting and I think I have an example for your investigation.

Thunderbird 1.5 JS Console error:
Error: Expected end of value for property but found 'repeat-y'. Error in
parsing value for property 'list-style-image'. Declaration dropped.
Source File: chrome://editor/skin/EditorDialog.css
Line: 360

View source of offending code:
/* ::::: Publishing Progress ::::: */

..progressitem[progress="busy"] {
list-style-image: url("chrome://editor/skin/icons/progress-busy.gif")
repeat-y top;
}

This error is what I get from the Sky Pilot Classic theme running on Tbird
1.5 using the 02062006 build of SPC. On FF I have the 02112006 build and
that build stopped reporting JS errors with that build.

At least now I know what the use of top is in the cited line of code.

Please visit the group that Gus has suggested as this query is OT in this
user support group.

--
Ron K.
Don't be a fonted, it's just type casting.