Document updates cause delayed crash?

[Clayton Drury <claytond@magna.com.au>]

Hi all,

I know that document.clear() doesn't work and that the 
workaround is
to use 
	document.close();
	document.open();

instead. I would like to know, however, if document.clear() does 
anything at all. If so, is it safe to leave it in my code?

On a related matter, how can I tell if a document is open or 
closed? I know that it is bad to force a close of a document 
while it is loading/laying out. How do I tell when load/layout 
is complete? I know of the onLoad method, but I also know that 
there are bugs with that too.

The document which I am working on has several frames. Selecting 
a link in one frame causes two other frames to redraw themselves 
with new text using writeln() statements (one also displays a 
gif (with width and height specified) when necessary). Is it 
possible for someone to select links in the first frame (thereby 
updating the other frames) fast enough that Navigator is 
attempting to close a document in another frame before the 
document has closed itself?

When I select lots of links rapidly the updates seem to occur in 
an orderly fashion, one after the other, but I quickly run into 
problems very soon after (Navigator sometimes crashes if I 
select something in one of the updated frames).

Any help on any of these topics would be greatly appreciated.

Thanks in advance.

Clayton Drury
New Logic.
--------------------------------------------------------------------
For help about the list, please send a message to 'majordomo@obscure.org'
with the message body 'help'. To unsubscribe, send a message to
'majordomo@obscure.org' with the message body 'unsubscribe javascript'.
List archives and pointer to FAQ: http://www.obscure.org/javascript/