Implement MediaMetadata artwork in content

content/renderer/media/android/renderer_media_session_manager.cc

Index: content/renderer/media/android/renderer_media_session_manager.cc
diff --git a/content/renderer/media/android/renderer_media_session_manager.cc b/content/renderer/media/android/renderer_media_session_manager.cc
index b5331c7472a30cacc4582ef5b350b0a0c67a6615..75ef0f5175157a555f87e7a2d19eaf50c24101b8 100644
--- a/content/renderer/media/android/renderer_media_session_manager.cc
+++ b/content/renderer/media/android/renderer_media_session_manager.cc
@@ -74,6 +74,16 @@ void RendererMediaSessionManager::SetMetadata(
   ipc_metadata.album =
       metadata.album.substr(0, MediaMetadata::kMaxIPCStringLength);
 
+  for (const auto& artwork : metadata.artwork) {
+    auto sanitized_artwork =
+        MediaMetadata::SanitizeArtwork(artwork);
+    if (sanitized_artwork)
+      ipc_metadata.artwork.push_back(sanitized_artwork.value());
+
+    if (ipc_metadata.artwork.size() >= MediaMetadata::kMaxNumberOfArtworkImages)

[DaleCurtis, 2016/06/29 17:20:20]

Is this necessary on the renderer side? I.e. it seems to assume an untrusted
browser?

[Zhiqiang Zhang (Slow), 2016/06/29 19:16:13]

I think we should. Otherwise the page may set a super long list of artwork, and
we don't want to send a message that long through IPC.

[DaleCurtis, 2016/07/01 00:01:04]

Ah, this is sending to the browser, not receiving. Gotcha.

+      break;
+  }
+
   Send(new MediaSessionHostMsg_SetMetadata(routing_id(),
                                            session_id,
                                            ipc_metadata));