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

ppapi/api/pp_codecs.idl

 /* Copyright (c) 2014 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 /**
  * Video profiles.
  */
 enum PP_VideoProfile {
   PP_VIDEOPROFILE_H264BASELINE = 0,
   PP_VIDEOPROFILE_H264MAIN = 1,
   PP_VIDEOPROFILE_H264EXTENDED = 2,
   PP_VIDEOPROFILE_H264HIGH = 3,
   PP_VIDEOPROFILE_H264HIGH10PROFILE = 4,
   PP_VIDEOPROFILE_H264HIGH422PROFILE = 5,
   PP_VIDEOPROFILE_H264HIGH444PREDICTIVEPROFILE = 6,
   PP_VIDEOPROFILE_H264SCALABLEBASELINE = 7,
   PP_VIDEOPROFILE_H264SCALABLEHIGH = 8,
   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
 };
 
 /**
  * Audio profiles.
  */
 enum PP_AudioProfile {
   PP_AUDIOPROFILE_OPUS = 0,
   PP_AUDIOPROFILE_MAX = PP_AUDIOPROFILE_OPUS
 };
 
@@ skipping 211 matching lines @@
   /**
    * The size, in bytes, of the bitstream data.
    */
   uint32_t size;
 
   /**
    * The base address of the bitstream data.
    */
   mem_t buffer;
 };