Allow hw secured codecs on chromecast

chromecast/browser/cast_content_window.cc

Index: chromecast/browser/cast_content_window.cc
diff --git a/chromecast/browser/cast_content_window.cc b/chromecast/browser/cast_content_window.cc
index cd7e7e231a4f5497b009ce2c54b86488118c4ba7..cedd78f98d76779c6e22d976d1e038b8a76a0c6a 100644
--- a/chromecast/browser/cast_content_window.cc
+++ b/chromecast/browser/cast_content_window.cc
@@ -9,10 +9,12 @@
 #include "base/threading/thread_restrictions.h"
 #include "chromecast/base/metrics/cast_metrics_helper.h"
 #include "chromecast/browser/cast_browser_process.h"
+#include "chromecast/chromecast_features.h"
 #include "content/public/browser/render_view_host.h"
 #include "content/public/browser/render_widget_host.h"
 #include "content/public/browser/render_widget_host_view.h"
 #include "content/public/browser/web_contents.h"
+#include "content/public/common/renderer_preferences.h"
 #include "ipc/ipc_message.h"
 #include "ui/display/display.h"
 #include "ui/display/screen.h"
@@ -113,6 +115,16 @@ std::unique_ptr<content::WebContents> CastContentWindow::CreateWebContents(
   content::WebContents* web_contents = content::WebContents::Create(
       create_params);
   content::WebContentsObserver::Observe(web_contents);
+
+#if !BUILDFLAG(DISABLE_DISPLAY)
+  content::RendererPreferences* prefs = web_contents->GetMutableRendererPrefs();
+  prefs->use_video_overlay_for_embedded_encrypted_video = true;

[ddorwin, 2016/05/24 22:05:41]

This is currently related directly to VIDEO_HOLE (and only used on Android via
AwSettings and Cast on Android). If Cast started using WMPI, this might create
unintended consequences (vs. the Ozone-based solution).

[yucliu1, 2016/05/24 22:26:33]

I found almost all the logics related to this boolean is inside android (except
the usage to select media key system config). Will the change break cast on
android or cast on all platforms (if cast use WMPI)?

Btw, what is WMPI, can you give some pointer?

[halliwell, 2016/05/24 22:51:02]

Yuchen: WMPI = WebMediaPlayerImpl
David, could you expand on your thoughts here?

This change doesn't affect Android or Cast on ATV as it stands, I think?  It's
making use of the same flag but on our linux+WMPI+Ozone pipeline.  Are you
talking about a future scenario where Cast on ATV starts using WMPI?

[ddorwin, 2016/05/24 23:11:50]

WMPI will soon be used for all EME content on Android (replacing WMPA).
Presumably, we will need to migrate the related WMPA logic there, which could
then have side effects on Chromecast.

At a higher level, though, this flag means "create a hole for EME video." That
is not necessarily the same thing as "use HW secure codecs," which we use as a
synonym for setting the security level in MediaDrmBridge.

+
+  content::RenderViewHost* host = web_contents->GetRenderViewHost();
+  if (host)
+    host->SyncRendererPrefs();
+#endif  // !BUILDFLAG(DISABLE_DISPLAY)
+
   return base::WrapUnique(web_contents);
 }