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

ppapi/api/pp_codecs.idl

Index: ppapi/api/pp_codecs.idl
diff --git a/ppapi/api/pp_codecs.idl b/ppapi/api/pp_codecs.idl
index 8699ec9853d9f9bf55555e16f6c3827493405801..a8b37fb8db6656c53d2fec5f2365bb898f4c6053 100644
--- a/ppapi/api/pp_codecs.idl
+++ b/ppapi/api/pp_codecs.idl
@@ -19,8 +19,11 @@ enum PP_VideoProfile {
   PP_VIDEOPROFILE_H264STEREOHIGH = 9,
   PP_VIDEOPROFILE_H264MULTIVIEWHIGH = 10,
   PP_VIDEOPROFILE_VP8_ANY = 11,
-  PP_VIDEOPROFILE_VP9_ANY = 12,

[raymes, 2016/03/29 01:51:49]

This looks like an API change. Is there potential for this to break existing
apps that use this?

[bbudge, 2016/03/29 21:42:12]

This is used by two Stable APIs (PPB_VideoDecoder, PPB_VideoEncoder), so in
general you have to create a new version of those APIs to modify any methods, or
any structs or enums used by those methods. You can see how new versions of
functions were added for those APIs in their IDL files (look for [version =
0.x]).

Probably the easiest thing for you to do is not modify Pepper. I don't know of
any plugin clients that are requesting more VP9 profiles.

-  PP_VIDEOPROFILE_MAX = PP_VIDEOPROFILE_VP9_ANY
+  PP_VIDEOPROFILE_VP9_PROFILE0 = 12,
+  PP_VIDEOPROFILE_VP9_PROFILE1 = 13,
+  PP_VIDEOPROFILE_VP9_PROFILE2 = 14,
+  PP_VIDEOPROFILE_VP9_PROFILE3 = 15,
+  PP_VIDEOPROFILE_MAX = PP_VIDEOPROFILE_VP9_PROFILE3
 };
 
 /**