Comment by jaffathecake
20 hours ago
Browser vendors want their browser to be safe to use. If we encourage users to essentially bake their own browser from a hodge podge of unverified third party code running at high privilege, we don't meet that goal.
An image codec can be run in a sandboxed way, with a preset cpu/ram boundary, the output is rastered pixels, how could this not be "safe"?
There are dozens of .wasm based image encoder/decoders outthere, no?
It's not like it could access network or IO, unlike extensions do, which could steal your data after authors sell their popular extension and buys profits from stealing data from installed users.