Previously expression sha3_512(<ArrayBuffer>) returned always the same value if <ArrayBuffer> was instance of ArrayBuffer and js-sha3 module was loaded using webpack no mater what value was stored in the ArrayBuffer object. It was caused by wrong recognition of ArrayBuffer argument since webpack loader doesn't call the topmost function with global object as an argument.
Coverage remained the same at 100.0% when pulling 9f8c2a3fb349cadd9f3e90065a05f74ae9adaee8 on happylynx:arraybuffer-fix into f34e33dc997bf85b3c5f12ec28b25a1068538249 on emn178:master.
Coverage remained the same at 100.0% when pulling 9f8c2a3fb349cadd9f3e90065a05f74ae9adaee8 on happylynx:arraybuffer-fix into f34e33dc997bf85b3c5f12ec28b25a1068538249 on emn178:master.
Coverage remained the same at 100.0% when pulling 9f8c2a3fb349cadd9f3e90065a05f74ae9adaee8 on happylynx:arraybuffer-fix into f34e33dc997bf85b3c5f12ec28b25a1068538249 on emn178:master.
Coverage remained the same at 100.0% when pulling 9f8c2a3fb349cadd9f3e90065a05f74ae9adaee8 on happylynx:arraybuffer-fix into f34e33dc997bf85b3c5f12ec28b25a1068538249 on emn178:master.
Previously expression
sha3_512(<ArrayBuffer>)
returned always the same value if<ArrayBuffer>
was instance ofArrayBuffer
andjs-sha3
module was loaded using webpack no mater what value was stored in the ArrayBuffer object. It was caused by wrong recognition of ArrayBuffer argument since webpack loader doesn't call the topmost function with global object as an argument.