Calls to setTimeout(..., 0) were previously clamped to a 1 ms timeout, instead of resulting in a callback as soon as possible. This clamping is being removed. To get the old behavior, use setTimeout(..., 1) instead.


Specification link

Specification being incubated in a Community Group

Status in Chromium


Removed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Last updated on 2021-06-19