Re:WebAssembly
by pjmlp on Sunday February 28, 2021 @01:07AM
(#26291062)
You cannot disable wasm.
[ Parent
| on HN ]
This isn't true. If you block javascript from running, then that will include blocking WebAssembly. WebAssembly is only started through javascript, and if things ever changes so that webpages can include WebAssembly directly, presumably it will also be controlled by the same browser settings that control whether javascript is executed.
Yeah, but then you block everything and not only wasm.
Why would you want to block wasm specifically? There's nothing it can do that javascript can't.
WebAssembly
WebAssembly {compile: ƒ, validate: ƒ, instantiate: ƒ, compileStreaming: ƒ, instantiateStreaming: ƒ, …}
delete WebAssembly
Uncaught ReferenceError: WebAssembly is not definedGreat, now do that in a check box like JavaScript settings on browsers, without extensions.
I have this running as a uBO scriptlet injected into every website before content javascript starts to execute
*##+js(myscript)
does various things, disables webassembly, websocket, AudioContext, serviceworkers, openDatabase and indexedDB, navigator.sendBeacon and window.opener, some fingerprinting randomization stuff, etc. I wish there was a Browser on the market actually letting you configure such things _per domain_ as Opera Presto used to, alas we are on our own now :(.