Richard Gration said the following on 6/30/2006 12:02 PM:
>> Richard Gration said the following on 6/30/2006 11:03 AM:
>>> On Fri, 30 Jun 2006 09:36:50 -0500, john wrote:
[quoted text clipped - 7 lines]
>
> I did test it. Did you?
I wouldn't be asking if I hadn't. Although I didn't have to test it to
know what it was going to do.
> It does exactly what I think it does in Opera 7.54, which is slow
> down execution.
The way it does it is the problem. It doesn't cause a pause, it causes
the UA to become unresponsive because the JS engine is executing code
during that pause. Using setInterval, or setTimeout, to cause a pause
doesn't cause the UA to freeze up.
> It might do more
It does, see above.
> ... what do you think it does?
Test it in IE and the freeze up becomes more obvious.

Signature
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Temporarily at: http://members.aol.com/_ht_a/hikksnotathome/cljfaq/
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Richard Gration - 30 Jun 2006 17:49 GMT
I'm perfectly well aware of setInterval and how it's superior due to the
fact that the delay loop causes unresponsiveness. All I wanted was a quick
easy way for the OP to see his progress bar ... err, progress. Hands up, I
missed a golden opportunity for didactic rambling, but there ya go, that's
me.