Bringing setTimeout to ECMAScript

Boris Zbarsky bzbarsky at MIT.EDU
Fri Mar 18 18:21:38 PDT 2011

On 3/18/11 7:26 PM, Brendan Eich wrote:
>> Two things off the top of my head to consider:
>>   - timer granularity
> This is an interop issue, mostly due to stupid benchmarks that degenerate to measuring whether the browser clamps at 10ms or 4ms. It is also now a standard: 4ms.

More precisely, the standard is "at least 4ms".

Browsers must delay nested timeouts by at least 4ms.  They can delay 
them by more if desired (and various browsers do or will in various 
circumstances: IE9 when on battery, Chrome and Firefox in background 
tabs, possibly other cases).


More information about the es-discuss mailing list