commit e79591b31f7374edbdd23c4b3c0b27301ba58475
author Miguel Casas <mcasas@chromium.org> Mon Jan 07 20:33:38 2019
committer Commit Bot <commit-bot@chromium.org> Mon Jan 07 20:33:38 2019
tree 9cd09d24b9f935f183cb0593f18899fae87d0cef
parent 7dc518f16a72aee29c945f596a2c57ec81b215e9

RELAND: MediaRecorder: only announce h264/avc1 support if RTC_USE_H264

The original CL got reverted because:
- It broke media_capabilities/encodingInfo.html
- It broke the MediaRecorder LayoutTests on non-Android bots
when RTC_USE_H264 is not defined (which is pretty pervasive, it turns
out). This CL then adds the necessary TestExceptions.


Original CL description ------------------------------------------------
Support for AVC1 encoding (a.k.a. H264) is dependent on RTC_USE_H264 [1],
but due to an omission, this was not tested when enumerating the video
codecs. This CL fixes that.

[1] https://cs.chromium.org/chromium/src/third_party/webrtc/webrtc.gni?type=cs&q=rtc_use_h264&sq=package:chromium&g=0&l=156

TBR=emircan@chromium.org

Bug: 809980, 719023
Change-Id: I0a1778adb0f5657ca1f06054d62a1a64b9d40ad6
Reviewed-on: https://chromium-review.googlesource.com/c/1395887
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#620078}
Reviewed-on: https://chromium-review.googlesource.com/c/1396452
Cr-Commit-Position: refs/heads/master@{#620453}