Recognize codec id vp9.2 as VP9 profile 2

media/base/mime_util_internal.cc

Index: media/base/mime_util_internal.cc
diff --git a/media/base/mime_util_internal.cc b/media/base/mime_util_internal.cc
index 031d548c7ced5e5e9b85f3f1d36481a2d751d4e7..fe463be566be29747ba66d43a68f8d2ec1a9ec6c 100644
--- a/media/base/mime_util_internal.cc
+++ b/media/base/mime_util_internal.cc
@@ -618,6 +618,9 @@ bool MimeUtil::StringToCodec(const std::string& mime_type_lower_case,
         // Profile 0 should always be supported if VP9 is supported.
         *is_ambiguous = false;
         break;
+      case VP9PROFILE_PROFILE2:
+        *is_ambiguous = false;
+        break;
       default:
         // We don't know if the underlying platform supports these profiles.

[ddorwin, 2016/12/08 02:08:01]

This statement does not seem true anymore. IsSupportedVideoConfig() should
answer this. In that case, it would seem that we do not need the profile switch
statement here and (for now - until we support levels, etc.) VP9 is not
ambiguous. (The profile extraction code should reject anything that is not 0-3.)

This assumes that all IsSupportedVideoConfig() implementations are implemented
correctly (only accepting 0 and maybe 2), which should be the case. However,
given the proposed Chrome implementation, we should verify this.

See also https://crbug.com/672327.

         // Need to add platform level querying to get supported profiles