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..4f2e55018d9de1ea76cf32cbbe606ff816fec647
--- /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.
+
+// https://w3c.github.io/mediacapture-record/MediaRecorder.html#MediaRecorderErrorEvent
+// https://w3c.github.io/mediacapture-record/MediaRecorder.html#idl-def-RecordingErrorNameEnum
+
+enum RecordingErrorNameEnum {
+    "InvalidState",
+    "OutOfMemory",
+    "IllegalStreamModification",
+    "SecurityError",
+    "OtherRecordingError"
+};
+
+[
+    NoInterfaceObject
+] interface MediaRecorderErrorEvent : Event {
+    readonly attribute RecordingErrorNameEnum name;

[esprehn, 2015/08/21 08:46:13]

Having a name property like this is very weird, I think you want to just fire a
DOMException and reuse the existing types for that. You're recreating that same
thing here, we already have InvalidState and SecurityError types. If you need
more error types please have them added for the DOMException.

[mcasas, 2015/08/21 18:50:05]

Seems like MediaRecordingError raises eyebrows in 
everyone reading it :)
but I just took it verbatim from the linked W3C draft.

Please advise, scrap it and reuse or comply?

+    readonly attribute DOMString? message;
+};