Fix illegal invocation of getRandomValues

[Nimelrian]

getRandomValues needs to be invoked in a context where "this" is a Crypto implementation. Binding the function to its respective Crypto implementation fixes the illegal invocation.

Fixes #256

[broofa]

Good catch!

[beck]

No test coverage?

[broofa]

Nope. Tests currently all run in node, but this is an IE 11 thing. Looking into setting up selenium tests somehow (e.g. Sauce Labs?) If you have suggestions or advice, 'happy to take a PR. :-)

[jsg2021]

3.2.0 is crashing in chrome too. Can the fix be published to npm?

[Nimelrian]

I bound the getRandomValues function of both, window.msCrypto (IE) and window.crypto (Edge, Chrome, FF). Works in all browsers which have one of the two implementations.

[broofa]

@jsg2021 This should be in npm as v3.2.1. Let me know if you still have issues.

[jsg2021]

thanks!

[beck]

this is an IE 11 thing

Tripped over this bug earlier this morning when unit testing some react code with enzyme.

Looking into setting up selenium tests somehow (e.g. Sauce Labs?) If you have suggestions or advice, 'happy to take a PR.

👍 - #260

Apologies for the large diff, scaffolding can be a bit painful/verbose. I tried to keep the boilerplate to a minimum.