MediaRecorder Blink part

LayoutTests/fast/mediarecorder/MediaRecorder-canRecordMimeType-expected.txt

Index: LayoutTests/fast/mediarecorder/MediaRecorder-canRecordMimeType-expected.txt
diff --git a/LayoutTests/fast/mediarecorder/MediaRecorder-canRecordMimeType-expected.txt b/LayoutTests/fast/mediarecorder/MediaRecorder-canRecordMimeType-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..1b54713ab71a16c45945aa995523a300b3ce4440
--- /dev/null
+++ b/LayoutTests/fast/mediarecorder/MediaRecorder-canRecordMimeType-expected.txt
@@ -0,0 +1,7 @@
+This is a testharness.js-based test.
+PASS check MediaRecorder.canRecordMimeType() with video/invalid 
+FAIL check MediaRecorder.canRecordMimeType() with video/webm and vp8 assert_equals: expected "maybe" but got ""

[Peter Beverloo, 2015/09/02 16:39:37]

Out of interest, aren't these tests going to fail when you implement the
Chromium-side of this change? If so, you may want to remove them now, and add
them after that lands. It saves you from a 3-sided patch, and means that you
don't have to check in failing expectations.

[mcasas, 2015/09/02 21:01:47]

Yeah, this was a conundrum, I didn't want to land all this code 
with no hints as to how it was supposed to work, in the form of
tests, but then I need to check the FAIL expectations. It'd be
great if I could commit a single CL that would "connect" with 
the Chrome classes and update the ...-expected.txt, ideas?

+PASS check MediaRecorder.canRecordMimeType() with audio/invalid 
+FAIL check MediaRecorder.canRecordMimeType() with audio/webm and opus assert_equals: expected "maybe" but got ""
+Harness: the test ran to completion.
+