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

content/renderer/pepper/pepper_video_decoder_host.cc

Index: content/renderer/pepper/pepper_video_decoder_host.cc
diff --git a/content/renderer/pepper/pepper_video_decoder_host.cc b/content/renderer/pepper/pepper_video_decoder_host.cc
index c8f3bd8ed9dc6f12665f35459599da3e8e62476d..d6895eb727e88083e02868d8822797fbbffad26f 100644
--- a/content/renderer/pepper/pepper_video_decoder_host.cc
+++ b/content/renderer/pepper/pepper_video_decoder_host.cc
@@ -65,7 +65,7 @@ media::VideoCodecProfile PepperToMediaVideoProfile(PP_VideoProfile profile) {
     case PP_VIDEOPROFILE_VP8_ANY:
       return media::VP8PROFILE_ANY;
     case PP_VIDEOPROFILE_VP9_ANY:
-      return media::VP9PROFILE_ANY;
+      return media::VP9PROFILE_PROFILE0;

[no sievers, 2016/03/31 17:20:42]

hmm why is this right?

[servolk, 2016/03/31 17:26:20]

This isn't 100% right, but that's essentially how we treat it today anyway, e.g.
look at
https://code.google.com/p/chromium/codesearch#chromium/src/content/common/gpu....
In the previous patchset I replaced PP_VIDEOPROFILE_VP9_ANY with 4 different
profile values, but then bbudge@ was concerned about changing PPAPI. So I've
decided to keep PPAPI unchanged for now (see
https://codereview.chromium.org/1769593002/#msg41). We can update it later if
necessary (if PPAPI decoders ever start caring about different VP9 profiles).

     // No default case, to catch unhandled PP_VideoProfile values.
   }