D
Derek
Hi,
I've built a rather large CGI that dumps a lot of data and a fairly
complex javascript app out to the client's browser. Granted this may
be poor style according to someone web design philosophy but that is
the way things need to work for now here. The problem I'm having is
that it appears that the browsers (IE, mozilla and netscape) are
sometimes getting confused about wether the javascript code is
running. By this I mean when I click a button that runs some filtering
functions on the data that was sent over by the CGI there are times
when it can take 10-15 seconds before the function finises executing.
But the filtering function always exits properly and when it does so
CPU utilization goes from 100% back to a normal 2-4% on my machine. At
this point I can continue to interact with the javascript app in my
browser, but sometimes the progress indicator in the status bar will
still keep moving as if processing is continuing in the background.
Also on occasion I've seen an error message pop-up (sometime during
but mostly after the filtering function) which says that the
javascript is making the browser run slowly do you want to continue.
After seeing this message the function has usually finished its work
so you click on yes to continue and everything is fine.
So, is there some way I can help the browser not loose track of the
fact that the javascript function has already returned?
And also is there a way to disable/prevent the browsers from
displaying the message about the javascript code causing the browser
to run slowly?
Finally what is the best way to give the users visible feedback that
the filtering function is working and that things aren't locked up?
The cursor doesn't change to the hourglass when the function is
running. And when I tried to output to another frame some progress
messages none of that data appeared in the frame until after the
filtering function had returned.
Thanks in advance for any help.
Derek
I've built a rather large CGI that dumps a lot of data and a fairly
complex javascript app out to the client's browser. Granted this may
be poor style according to someone web design philosophy but that is
the way things need to work for now here. The problem I'm having is
that it appears that the browsers (IE, mozilla and netscape) are
sometimes getting confused about wether the javascript code is
running. By this I mean when I click a button that runs some filtering
functions on the data that was sent over by the CGI there are times
when it can take 10-15 seconds before the function finises executing.
But the filtering function always exits properly and when it does so
CPU utilization goes from 100% back to a normal 2-4% on my machine. At
this point I can continue to interact with the javascript app in my
browser, but sometimes the progress indicator in the status bar will
still keep moving as if processing is continuing in the background.
Also on occasion I've seen an error message pop-up (sometime during
but mostly after the filtering function) which says that the
javascript is making the browser run slowly do you want to continue.
After seeing this message the function has usually finished its work
so you click on yes to continue and everything is fine.
So, is there some way I can help the browser not loose track of the
fact that the javascript function has already returned?
And also is there a way to disable/prevent the browsers from
displaying the message about the javascript code causing the browser
to run slowly?
Finally what is the best way to give the users visible feedback that
the filtering function is working and that things aren't locked up?
The cursor doesn't change to the hourglass when the function is
running. And when I tried to output to another frame some progress
messages none of that data appeared in the frame until after the
filtering function had returned.
Thanks in advance for any help.
Derek