Add 4 VP9 profiles to the media::VideoCodecProfile enum.

content/renderer/pepper/ppb_video_decoder_impl.cc

Index: content/renderer/pepper/ppb_video_decoder_impl.cc
diff --git a/content/renderer/pepper/ppb_video_decoder_impl.cc b/content/renderer/pepper/ppb_video_decoder_impl.cc
index 5c5fcb224a39fe509ce140380deec210274bfaca..17acfe881f6688aac3b4273b8534d5f34d33e869 100644
--- a/content/renderer/pepper/ppb_video_decoder_impl.cc
+++ b/content/renderer/pepper/ppb_video_decoder_impl.cc
@@ -67,6 +67,14 @@ media::VideoCodecProfile PPToMediaProfile(
       return media::H264PROFILE_MULTIVIEWHIGH;
     case PP_VIDEODECODER_VP8PROFILE_ANY:
       return media::VP8PROFILE_ANY;
+    case PP_VIDEODECODER_VP9PROFILE_PROFILE0:

[fgalligan1, 2016/03/23 18:14:08]

Will this be fine? Currently this decoder does not have support for vp9.

[servolk, 2016/03/24 18:05:43]

Yes, I believe this should be fine. This simply allows translation from
PP_VideoDecoder_Profile into media::VideoCodecProfile (note that all other
profile values are also not checked to be supported here and are merely
translated). The actual check whether this is a supported profile or not is
going to happen in one of the several implementations of
media::VideoDecodeAccelerator interface. E.g. inside
VaapiVideoDecodeAccelerator::Initialize for VAAPI.

+      return media::VP9PROFILE_PROFILE0;
+    case PP_VIDEODECODER_VP9PROFILE_PROFILE1:
+      return media::VP9PROFILE_PROFILE1;
+    case PP_VIDEODECODER_VP9PROFILE_PROFILE2:
+      return media::VP9PROFILE_PROFILE2;
+    case PP_VIDEODECODER_VP9PROFILE_PROFILE3:
+      return media::VP9PROFILE_PROFILE3;
     default:
       return media::VIDEO_CODEC_PROFILE_UNKNOWN;
   }