media: Add test to ensure encrypted VP9 profile 1/2/3 are not supported

chrome/browser/media/encrypted_media_supported_types_browsertest.cc

Index: chrome/browser/media/encrypted_media_supported_types_browsertest.cc
diff --git a/chrome/browser/media/encrypted_media_supported_types_browsertest.cc b/chrome/browser/media/encrypted_media_supported_types_browsertest.cc
index 79e575b77b63b2829552386f3024260950f73f8b..a782ea2e86edd1fbbcef57a5d04997d73a52febb 100644
--- a/chrome/browser/media/encrypted_media_supported_types_browsertest.cc
+++ b/chrome/browser/media/encrypted_media_supported_types_browsertest.cc
@@ -130,8 +130,15 @@ class EncryptedMediaSupportedTypesTest : public InProcessBrowserTest {
 #endif
 
     // Codecs allowed by both MP4 and WebM (with given command line flags).
+    // For vp9 codec string format, see https://www.webmproject.org/vp9/mp4/
     video_common_codecs_.push_back("vp09.00.10.08");
 
+    // Non-zero VP9 profiles are not yet supported, even with the given command
+    // line flags. See http://crbug.com/707128
+    invalid_codecs_.push_back("vp09.01.10.08");
+    invalid_codecs_.push_back("vp09.02.10.10");
+    invalid_codecs_.push_back("vp09.03.10.10");
+
     // Extended codecs are used, so make sure generic ones fail. These will be
     // tested against all initDataTypes as they should always fail to be
     // supported.