4 ms·

I find the following in Chrome: > window.crypto.getRandomValues // getRandomValues() { [native code] } > window.crypto.getRandomValues = function () { return

I find the following in Chrome: > window.crypto.getRandomValues // getRandomValues() { [native code] } > window.crypto.getRandomValues = function () { return "aloha" } > window.crypto.getRandomValues() // "aloha" Not sure if this is the case in all browsers. `window.crypto` certainly should be read-only.

niftich 10y ago
In Chrome, window.crypto is read-only: > window.crypto < Crypto {subtle: SubtleCrypto} > window.crypto = "hi!" < "hi!" > window.crypto < Crypto {subtle: SubtleCrypto} But not anything underneath, including getRandomValues(), as you write. A recent issue about this [1] on the WebCrypto spec itself was closed with 'wontfix' because in their view, polyfilling web APIs is a common and accepted practice. [1] https://github.com/w3c/webcrypto/issues/107 https://github.com/w3c/webcrypto/issues/107
- flukus 10y ago
  Shouldn't all pollyfills check only override the functions if they're missing?
  - jsjohnst 10y ago
    What if it's present but the implementation is incomplete?
    - paulddraper 10y ago
      E.g. an extra optional parameter.