Block JavaScript from using JIT on these sites

Allows you to set a list of site url patterns that specify sites which are not allowed to run JavaScript JIT (Just In Time) compiler enabled.

Disabling the JavaScript JIT will mean that Google Chrome may render web content more slowly, and may also disable parts of JavaScript including WebAssembly. Disabling the JavaScript JIT may allow Google Chrome to render web content in a more secure configuration.

For detailed information on valid url patterns, please see https://chromeenterprise.google/policies/url-patterns. Wildcards, *, are allowed.

Policy exceptions can be set for specific subdomains as well as entire sites. For example, a policy set for only subdomain.site.com applies to subdomain.site.com without affecting site.com. In some cases where a subdomain cannot be isolated from its parent site, it may inherit the policy set on site.com. Exceptions may also not take effect for frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced, and sites will instead use the policy from DefaultJavaScriptJitSetting, if set, or default to the profile's JavaScript JIT setting.

To enforce exceptions, Google Chrome may place sites or subdomains whose setting differs from the default into dedicated processes. This can increase memory usage, especially on Android or when a wildcard pattern matches many subdomains, since each matching origin may be isolated separately. Isolated subdomains also cannot use document.domain to access their parent site.

Note: In versions 155 and earlier, policy exceptions were only enforced at a site granularity (eTLD+1). A policy set for only subdomain.site.com did not take effect, even for subdomain.site.com; it had to be set on site.com to apply to both site.com and subdomain.site.com.

This policy applies on a frame-by-frame basis and not based on top level origin url alone, so e.g. if site-one.com is listed in the JavaScriptJitBlockedForSites policy but site-one.com loads a frame containing site-two.com then site-one.com will have JavaScript JIT disabled, but site-two.com will use the policy from DefaultJavaScriptJitSetting, if set, or default to JavaScript JIT enabled. Blocklist entries have higher priority than allowlist entries, which in turn have higher priority than the configured default value.

If this policy is not set for a site then the policy from DefaultJavaScriptJitSetting applies to the site, if set, otherwise JavaScript JIT is enabled for the site.

Example value:

[*.]example.edu