RTCCertificate and RTCPeerConnection.generateCertificate added to JavaScript

Source/modules/mediastream/RTCPeerConnection.idl

Index: Source/modules/mediastream/RTCPeerConnection.idl
diff --git a/Source/modules/mediastream/RTCPeerConnection.idl b/Source/modules/mediastream/RTCPeerConnection.idl
index fa5494606e720f8f19b2043bc0492e96f623dd77..aa5fde1dc3b4895e2aea46ee58c212128359d575 100644
--- a/Source/modules/mediastream/RTCPeerConnection.idl
+++ b/Source/modules/mediastream/RTCPeerConnection.idl
@@ -48,8 +48,11 @@
 
     readonly attribute DOMString signalingState;
 
+    // FIXME: Latest WebRTC specifications renames this to setConfiguration
     [RaisesException] void updateIce(optional Dictionary configuration, optional Dictionary mediaConstraints);
 
+    [RuntimeEnabled=RTCCertificate, RaisesException, CallWith=ScriptState] static Promise<RTCCertificate> generateCertificate(Dictionary keygenAlgorithm);

[jochen (gone - plz use gerrit), 2015/09/15 08:04:19]

this should be AlgorithmIdentifier, not Dictionary, no?

[hbos_chromium, 2015/09/21 16:12:22]

You're right. It should be a WebCryptoAPI AlgorithmIdentifier, which is an
object (Dictionary) or DOMString that is parsed. I took a look at this after
your comment.

Currently I'm doing the parsing myself. What I should be using is the
WebCryptoAPI normalization process which parses it for us. I tried to do this,
but I believe I've found a WebCryptoAPI bug. If I try to parse what the WebRTC
spec says must be supported, normalizeAlgorithm() complains that the
publicExponent parameter is not an Uint8Array. I have filed a bug
(crbug.com/534416) with rsleevi@ CC'd.

In the meantime I've added a TODO.

+
     // DEPRECATED
     [RaisesException] void addIceCandidate(RTCIceCandidate candidate);