Increase the nesting threshold before which setTimeout(..., <4ms) start being clamped, from 5 to 100.
TAG review status
Interoperability and Compatibility
setTimeout is a well established and mature API. This change poses a risk of breaking websites and tests that rely on the current clamping behavior and the subtle task ordering that it entails.
As an example, this change breaks the assumption that setTimeout(0) causes micro tasks to run in at least one case in Chrome tests (crbug.com/1302309).
On the flip side, the implementation in Chrome is already non compliant (crbug.com/1108877). There's also a similar experiment on beta that is ongoing (crbug.com/1263190).
Devs can use chrome://flags#unthrottled-nested-timeout to test their sites for compatibility issues.Gecko
: No signalWebKit
: No signalWeb developers
: No signalsOther signals
setTimeout() and setInterval() have an associated trace event in DevTools.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Requires code in //chrome?
Link to entry on the Chrome Platform Status