support Web Crypto API inside a Web Worker

External Issue #7607496


Unsung H.
May 19, 2016
This issue is public.
Found in
  • Microsoft Edge
Reported by 9 people

Sign in to watch or report this issue.

Steps to reproduce

The Web Crypto API is not available inside a Web Worker. Both “self.crypto” and “self.msCrypto” are undefined inside a worker context.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Venkat K.”

      Changed Status to “External”

    • This is on our backlog for a future release. We have duped your item of feedback here to an internal deliverable.  Thanks for your feedback!

      All the best,
      The MS Edge Team

    • Hi, Is there a scheduld to support WebCrypto in web worker? (IE & Edge)

    • We just hit this in and aren’t sure how to work around it. Math.random just isn’t a good idea. Are there any recommended ways what to do until this is supported?

    • I would like to add another vote for escalating this ASAP.
      We are now advising one large client (over 20K windows desktop endpoints) with specific end-to-end file upload encryption requirements to use Chrome and Firefox until this is resolved.

    • We need it dearly for our Ghostery extension, which utilizes crypto in Worker on all other browsers, but have to limit functionality on Edge.

    • This affects ServiceWorker as well and limits its usability dramatically.

    • I have a use case for Web Crypto in Service Worker.

    • This is a big deal for me. Any idea when will it be available?

    • This just became a larger issue due to a recent change in Emscripten, where the library now throws in Edge:

      This basically breaks our current solution, and there’s no clear path to fix it, other than forking Emscripten and adding Math.random() back in, which is terrible.

    You need to sign in to your Microsoft account to add a comment.

    Sign in