|
There are several Issues that are a bit tricky due to asynchronous (thread based!) processing in Browsers
|
This is seen in reloading JavaScript pages. This produces unclear results as different frames and associated JavaScript variables are set in adifferent order from that in which multi-frame system was built!
-
Often get "false" errors as variables not set "in time"
|
In self-documenting pages: one
-
First requests page to be loaded (say from top frame) by setting location property for frame.
-
The Javascript code in top continues without waiting for page to be loaded
-
Thus you need to know when information has been loaded -- this is purpose of top.AccumulateInfoPage('processit!'); call
|
