UnthrottledNestedTimeoutEnabled

setTimeout(…, 0) is commonly used to break down long Javascript tasks. When the policy is set to Enabled, setTimeouts and setIntervals with an interval smaller than 4ms are not clamped as aggressively. This improves short horizon performance, but websites abusing the API will still eventually have their setTimeouts clamped. When the policy is set to Disabled, setTimeouts and setIntervals with an interval smaller than 4ms will be clamped. This may change task ordering on a web page, leading to unexpected behavior on sites that are dependent on a certain ordering in some way. It also may affect sites with a lot of setTimeout() with a timeout of 0ms usage, e.g. increasing CPU load. For users where this policy is unset, Google Chrome will roll out the change gradually on the stable channel. This is a temporary policy that is planned be removed in Google Chrome 107. This deadline may be extended if there is a need for it among enterprises.