disable-webassembly

disable-webassembly copied to clipboard

Preface

I tested about:blank and some other sites that use WASM against the SO script mentioned in #2 .

Tested on Edge 136 (latest)

Manual

Flags to disable in edge://flags:

• #enable-webassembly-baseline
• #enable-webassembly-lazy-compilation
• #enable-webassembly-tiering
• #enable-experimental-webassembly-features (disabled by default)

All of these flags are available for Mac, Windows, Linux and Android.

Command-line

The equivalent Batch command, as generated by Edge in edge://version:

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --restart --flag-switches-begin --disable-features=WebAssemblyBaseline,WebAssemblyLazyCompilation,WebAssemblyTiering --flag-switches-end

In short-form:

"%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" --restart --flag-switches-begin --disable-features=WebAssemblyBaseline,WebAssemblyLazyCompilation,WebAssemblyTiering --flag-switches-end

Or in PowerShell:

Start-Process msedge -ArgumentList '--restart --flag-switches-begin --disable-features=WebAssemblyBaseline,WebAssemblyLazyCompilation,WebAssemblyTiering --flag-switches-end'

Upon testing, even after terminating all Edge processes, none of these commands affect the flags or prevent the WASM engine from being exposed. And as expressed in #2 , the --js-flags=--noexpose_wasm command-line argument does not work, either.

Conclusion

Unless there's something to be gained from other flags, I don't know of any way to disable WASM in Edge, and so I would like to open this issue up to discussion.