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

Policy overview

Key metadata and intent for this policy.

Category
Microsoft Edge
Supported on
Microsoft Edge version 105, Windows 7 or later

Supported OS tags: Windows7

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.

Internal name
UnthrottledNestedTimeoutEnabled
Policy ID
c81534766ad5
Elements
0

Registry values

How enabled and disabled states update the registry.

ScopeRegistry locationTypeEnabled valueDisabled valueCopy
Path
Software\Policies\Microsoft\Edge
Value name
UnthrottledNestedTimeoutEnabled
REG_DWORD
HKLM
1
HKCU
1
HKLM
0
HKCU
0
Registry location
Type REG_DWORD · Both
Path
Software\Policies\Microsoft\Edge
Value name
UnthrottledNestedTimeoutEnabled
Hive
HKLM
Enabled value
1
Disabled value
0
Hive
HKCU
Enabled value
1
Disabled value
0

Policy elements

Inputs and configuration options exposed by this policy.

This policy has no additional user input fields.