[webcrypto] Implicitly set public keys to extractable.

There was consensus on this issue during TPAC, and this behavior will be called out in a forthcoming spec update.

See also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23695

BUG=245025

Review URL: https://codereview.chromium.org/104923004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239109 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/content/renderer/webcrypto/webcrypto_impl.cc b/content/renderer/webcrypto/webcrypto_impl.cc
index a977b946..4e343ba8 100644
--- a/content/renderer/webcrypto/webcrypto_impl.cc
+++ b/content/renderer/webcrypto/webcrypto_impl.cc
@@ -228,11 +228,7 @@
       DCHECK(private_key.handle());
       DCHECK_EQ(algorithm.id(), public_key.algorithm().id());
       DCHECK_EQ(algorithm.id(), private_key.algorithm().id());
-      // TODO(padolph): The public key should probably always be extractable,
-      // regardless of the input 'extractable' parameter, but that is not called
-      // out in the Web Crypto API spec.
-      // See https://www.w3.org/Bugs/Public/show_bug.cgi?id=23695
-      DCHECK_EQ(extractable, public_key.extractable());
+      DCHECK_EQ(true, public_key.extractable());
       DCHECK_EQ(extractable, private_key.extractable());
       DCHECK_EQ(usage_mask, public_key.usages());
       DCHECK_EQ(usage_mask, private_key.usages());