MediaRecorder Blink part

Source/modules/mediastream/MediaRecorderErrorEvent.idl

Index: Source/modules/mediastream/MediaRecorderErrorEvent.idl
diff --git a/Source/modules/mediastream/MediaRecorderErrorEvent.idl b/Source/modules/mediastream/MediaRecorderErrorEvent.idl
new file mode 100644
index 0000000000000000000000000000000000000000..361ff9375490426ce8dec123344a00c103607fc5
--- /dev/null
+++ b/Source/modules/mediastream/MediaRecorderErrorEvent.idl
@@ -0,0 +1,21 @@
+// Copyright 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// http://w3c.github.io/mediacapture-record/MediaRecorder.html#MediaRecorderErrorEvent
+// http://w3c.github.io/mediacapture-record/MediaRecorder.html#idl-def-RecordingErrorNameEnum

[Peter Beverloo, 2015/07/29 16:54:22]

nit: https

[mcasas, 2015/07/30 13:20:37]

Done.

+
+enum RecordingErrorNameEnum {

[Peter Beverloo, 2015/07/29 16:54:22]

Huh? I find this odd API design. 

Why doesn't the specification drop all of 6.2-6.4 and use actual DOMExceptions
instead? (I realize that you may not have the answer.)

[mcasas, 2015/07/30 13:20:37]

I don't know, the W3C spec is a bit old so it's not impossible
that is outdated. Then again, this MediaRecorderErrorEvent
was added after the original Draft was written. 

Should I add a TODO() and ping the W3C, or any other
suggestions...?

+    "InvalidState",
+    "OutOfMemory",
+    "IllegalStreamModification",
+    "SecurityError",
+    "OtherRecordingError"
+};
+
+[
+    NoInterfaceObject
+] interface MediaRecorderErrorEvent : Event {
+  readonly attribute RecordingErrorNameEnum name;
+  readonly attribute DOMString? message;

[Peter Beverloo, 2015/07/29 16:54:22]

nit: four space indent.

[mcasas, 2015/07/30 13:20:37]

Done.

+};