You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Main thread] waiting for libsodium
[Main thread] libsodium ready
Starting worker …
[Worker] waiting for libsodium
[Worker] libsodium ready
On Edge 16, the output only contains
[Main thread] waiting for libsodium
[Main thread] libsodium ready
Starting worker …
[Worker] waiting for libsodium
When adding the crypto polyfill from @buu700#46 (comment) (slightly modified to be usable in strict mode) to cryptoworker.js (cryptoworker.js.txt), everything works.
This brings me to two questions:
Why is .ready not rejected when crypto is missing?
Why is a random number generator required before any libsodium function is called? Maybe I just need some Argon2 and do not need a RNG.
The text was updated successfully, but these errors were encountered:
This happens because _sodium_init() never returns in
(function(root){functionexpose_wrappers(exports,libsodiumModule){"use strict";varoutput_format="uint8array";varlibsodium;varready=libsodiumModule.ready.then(function(){libsodium=libsodiumModule;if(libsodium._sodium_init()!==0){thrownewError("libsodium was not correctly initialized.");}// ...
Steps to reproduce:
Expected: log output contains
On Edge 16, the output only contains
When adding the crypto polyfill from @buu700 #46 (comment) (slightly modified to be usable in strict mode) to cryptoworker.js (cryptoworker.js.txt), everything works.
This brings me to two questions:
The text was updated successfully, but these errors were encountered: