media: Remove Vorbis from secure decoder list for Widevine.

chrome/common/chrome_content_client.cc

Index: chrome/common/chrome_content_client.cc
diff --git a/chrome/common/chrome_content_client.cc b/chrome/common/chrome_content_client.cc
index a956d00c50fb119e58f3dfda3aaa367ce239bb12..d3a3f4fdde5b76f37d75fcc261cbf55025e25553 100644
--- a/chrome/common/chrome_content_client.cc
+++ b/chrome/common/chrome_content_client.cc
@@ -172,8 +172,8 @@ void ComputeBuiltInPlugins(std::vector<content::PepperPluginInfo>* plugins) {
           kWidevineCdmPluginMimeTypeDescription);
 
       // Add the supported codecs as if they came from the component manifest.
+      // This list must match the CDM that is being bundled with Chrome.

[Lei Zhang, 2016/02/12 21:34:17]

Is there any way to test and assert this is true?

[xhwang, 2016/02/12 21:39:15]

We can bundle the manifest file with the CDM. Then only populate these codec
info from the manifest file.

ddorwin: WDYT?

[ddorwin, 2016/02/12 21:43:32]

This should be part of a larger effort to unify the component and non-component
paths.

[xhwang, 2016/02/12 21:53:16]

Agreed. I filed a bug to track this work:
https://code.google.com/p/chromium/issues/detail?id=586634

       std::vector<std::string> codecs;
-      codecs.push_back(kCdmSupportedCodecVorbis);
       codecs.push_back(kCdmSupportedCodecVp8);
       codecs.push_back(kCdmSupportedCodecVp9);
 #if defined(USE_PROPRIETARY_CODECS)