I’m confused, it seems like they’ve changed this behavior now between Chromium 122.0.6261.57 and 122.0.6261.94.
On the latest version if I go to test whether WebAssembly is enabled on a site like https://wasm-feature-detect.surma.technology/ it shows that it is enabled despite “Don’t allow sites to use the V8 optimizer” being set.
I guess this is intentional, so changing this setting isn’t truly, completely JITless as the enterprise policy name would suggest:
https://issues.chromium.org/issues/325992828
As of r1247811, there is a new site setting, which is entitled “Sites
can use the V8 optimizer”. The actual behavior of that setting, though,
is that it disables all use of JIT in the renderer, which means
disabling WebAssembly support altogether.Since M122 is going to stable imminently, this change is the minimal fix
to avoid breaking an existing web API (wasm): the site setting’s
behavior is changed to match what the settings page describes. Since
this setting is also tied to enterprise policies:
- DefaultJavaScriptJitSetting
- JavaScriptJitAllowedForSites
- JavaScriptJitBlockedForSites
This change will cause a behavior change for users of those policies:
webassembly will be enabled for sites for which it would previously have
been disabled.
I don’t understand why this (highlighted) was considered a bug.
Edit: In https://issues.chromium.org/issues/325974501 they indicate this might be fixed in 123.