WebKit nightlies and Safari 3 disregard any timers less than 10ms and according to this article so does IE and Firefox. See the section titled "(3) JS Timeouts and Intervals" here: http://webkit.org/blog/?p=96
-- Brandon Aaron On 8/26/07, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > > > Pops schrieb: > > So who knows what the developer of this code was thinking when he/she > > set this value to 1. Maybe you do need it for animation. Maybe he had > > yahoo finance running at the time and it mistakely thought that 1ms is > > the "Fastest Possible" when it fact it is not. Zero ms is the > > fastest. The problem is that 0ms is so fast, it will create a massive > > CPU hogging. So you don't want 0ms. > Here is one resource about minimum timeout values: > http://dev.opera.com/articles/view/efficient-javascript/?page=2#timeouts > (last paragraph). > Not exactly accurate, but at least a better rule of thumb then just > guessing in the wild. > > -- Jörn >
