Image decode color: Push color profile from browser to renderer

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index 80535bd5241f15e5ee2348b02388ca1fac55e23c..d87aedc84e57d3fb9727c83f03782dee08b98f9e 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -739,6 +739,7 @@ void RenderViewImpl::Initialize(const ViewMsg_New_Params& params,
       command_line.HasSwitch(switches::kRootLayerScrolls));
   webview()->setShowFPSCounter(
       command_line.HasSwitch(cc::switches::kShowFPSCounter));
+  webview()->setDeviceColorProfile(params.image_decode_color_profile);

[ccameron, 2016/03/15 06:02:24]

We should not consider this to be the permanent home of the
image_decode_color_profile.

I argue that this is appropriate *for now* because it reflects that the profile
is just once at initialization (unlike other IPCs like ViewMsg_Resize or
ViewMsg_ColorProfile, which can be sent multiple times).

When image decode color profile is dynamic in the renderer, ViewMsg_Resize or
ViewMsg_ColorProfile will be a better match for this functionality. But not now.

Of note is that because this is setting a static variable via initialization,
only the first call in this process will "count". While I wouldn't argue that to
be an ideal arrangement, I think it's the best we can do for the moment.

 
   ApplyWebPreferencesInternal(webkit_preferences_, webview(), compositor_deps_);