JavaScript setTimeout will not be clamped until a higher nesting threshold is set (deprecated)

DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. This policy is deprecated because it's a temporary policy for web standards compliance. It doesn't work in Microsoft Edge version 107 onward. If you enable this policy, the JavaScript setTimeout and setInterval, with an interval smaller than 4 ms, aren't clamped. This improves short horizon performance; however, websites abusing the API still have their setTimeout usages clamped. If you disable or don't configure this policy, the JavaScript setTimeout and setInterval, with an interval smaller than 4 ms, are clamped. This is a web standards compliancy feature that changes task ordering on a webpage, leading to unexpected behavior on sites that are dependent on a certain ordering. It also affects sites with a lot of usage of a timeout of 0 ms for setTimeout, for example, increasing CPU load.