On 9 déc, 07:16, Kelly Norton <[EMAIL PROTECTED]> wrote: > > Chrome: 4ms (fairly recent change) > Safari (mac): 10ms > Safari (win): 15ms > Firefox: 15ms (or 10ms if flash is running) > IE: 15ms > Opera: I have no clue. > > So, that's just a really long way of saying that there is no danger in > allowing 0 and technically it is a perfectly legal value ... it's just > not very useful.
I'd add FWIW that HTML5 (pending a split into a distinct spec) defines setTimeout and setInterval as to "asynchronously wait timeout milliseconds and then queue a task [...]" http://www.whatwg.org/specs/web-apps/current-work/multipage/no.html#timers --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
