[webcrypto] Make it safe to delete WebCryptoResult from any thread.

public/platform/WebCrypto.h

Index: public/platform/WebCrypto.h
diff --git a/public/platform/WebCrypto.h b/public/platform/WebCrypto.h
index d9a1fb4a328da6fc7ee6b76260dec6b2b219b2e2..edf5ab52b88aaf35814603b9658172885a52da9c 100644
--- a/public/platform/WebCrypto.h
+++ b/public/platform/WebCrypto.h
@@ -139,19 +139,21 @@ public:
     // Threading
     // -----------------------
     //
-    // The WebCrypto interface will only be called from the render's main
-    // thread. All communication back to Blink must be on this same thread.
+    // The WebCrypto interface will be called from blink threads (main or
+    // web worker). All communication back to Blink must be on this same thread.
+    //
     // Notably:
     //
-    //   * The WebCryptoResult is NOT threadsafe. It should only be used from
-    //     the Blink main thread.
+    //   * The WebCryptoResult can be copied between threads, however all
+    //     methods other than the destructor must be called from the origin
+    //     Blink thread.
     //
     //   * WebCryptoKey and WebCryptoAlgorithm ARE threadsafe. They can be
     //     safely copied between threads and accessed. Copying is cheap because
     //     they are internally reference counted.
     //
     //   * WebArrayBuffer is NOT threadsafe. It should only be created from the
-    //     Blink main thread. This means threaded implementations may have to
+    //     target Blink thread. This means threaded implementations may have to
     //     make a copy of the output buffer.
     //
     // -----------------------