again: foreign page finished loading

[Andreas Leue]

Hi,

I am writing a small, automated webapp-test-machine
in javascript. It shall work with something like
Mozilla/Netscape - IE is not a choice.
In this context it is necessary to detect when a
page finished loading
- without having access to that foreign page and
- without being in a parent-frame of that page
I have consulted this group as well as other sources,
read many articles, but this specific issue seems
to be not solvable, true?
It does not have to be browser independent (it would
be nice if, though), but all my experiemnts with
events and onload handlers and alike were successless.
Even checking window.status seems not to work predictable.

Before desperating - is there any hope?

Thanks in advance for any help,
Andreas

[VK]

Re: again: foreign page finished loading

You cannot do it.
Not because JavaScript is so badly written, but because it's build to
protect end users from the situations when their browsers becoming a source
of hacker attacks.

Besides everything else, it doesn't allow parents (windows) to abuse their
children (windows). The logic is very simple: every child has window.opener
reference to send any information it wants to its parent (including its
status). If it doesn't, it means it doesn't want to, and the parent has no
power to force it.

Imaging we could freely track events in other windows, let's say keyPress.
"Yummy!" for any hacker.

You may want to write a small HTML-parser on Java instead.


Andreas Leue <al@sphenon.d e> wrote in message
news:m3y8wehs09 .fsf@islay.sphe non.de...[color=blue]
> Hi,
>
> I am writing a small, automated webapp-test-machine
> in javascript. It shall work with something like
> Mozilla/Netscape - IE is not a choice.
> In this context it is necessary to detect when a
> page finished loading
> - without having access to that foreign page and
> - without being in a parent-frame of that page
> I have consulted this group as well as other sources,
> read many articles, but this specific issue seems
> to be not solvable, true?
> It does not have to be browser independent (it would
> be nice if, though), but all my experiemnts with
> events and onload handlers and alike were successless.
> Even checking window.status seems not to work predictable.
>
> Before desperating - is there any hope?
>
> Thanks in advance for any help,
> Andreas[/color]