<SCRIPT SRC="filename.js"></SCRIPT> method.
events. Again the images I use are pre-cached before use, and everything is fine ... until ...
... I cause another window to launch when clicking on a link.
... in both cases I Explorer decides in its "wisdom" to totally ignore the fact that it has the images I mentioned above already cached,
and requests them all again from the server.
Naturally, ( as you can imagine ) because the clock function I have written is now up and running and rescheduling itself, this
messes up the works good style and everything grinds to a halt :-(.
Please note that the problem descibed above does not occur at all when using Netscape Navigator, my preferred browser anyway.
In this case no requests are made to the server, and I have proved this by monitoring TCP/IP activity.
Any help anyone can offer would be appreciated.
Many thanks in advance
Both script-using frames use locally scoped variables with no overlap or name duplication at any level in the scoping chain, so IE has no "excuse" to go and re-check them out by requesting frame image updates from the server.
(edited by: tedster at 3:42 am (gmt) on Aug. 22, 2001)