Send the ICC profile to the compositor under aura.

content/browser/renderer_host/render_widget_host_view_aura.cc

Index: content/browser/renderer_host/render_widget_host_view_aura.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_aura.cc b/content/browser/renderer_host/render_widget_host_view_aura.cc
index c681785cb705010ce713840ddd9c68ad69bc198e..0269d73a117ef22327afe4d024a2734ec3236f49 100644
--- a/content/browser/renderer_host/render_widget_host_view_aura.cc
+++ b/content/browser/renderer_host/render_widget_host_view_aura.cc
@@ -2672,6 +2672,8 @@ void RenderWidgetHostViewAura::AddedToRootWindow() {
   UpdateLegacyWin();
 #endif
 
+  window_->GetHost()->compositor()->SetDisplayColorSpace(
+      gfx::ICCProfile::FromBestMonitor().GetColorSpace());

[piman, 2016/09/02 23:23:38]

Drive-by: why is this done here, it's odd...

This function has to do with when a tab is added/removed from a window, on a
per-renderer basis.
Should a window without a renderer not have a color profile?
Do we need to reset this color profile every time a new tab gets created, or
gets moved to another window? I seems unrelated.

Couldn't we just do this in the ui::Compositor constructor if we're going to
pick an arbitrary monitor anyway?

[hubbe, 2016/09/02 23:27:48]

I'll let ccameron@ answer, I put it here because he suggested it..

[ccameron, 2016/09/02 23:41:48]

Sorry, you're right. On Mac we send this from the RWHVMac (and we do support
multi-monitor there). Aura will need to be different.

A more reasonable place, for now, may be at:
https://cs.chromium.org/chromium/src/ui/aura/window_tree_host.cc?rcl=14728439...
Eventually it will need to be updated when:
 - The Aura window moves to a different monitor
 - The system's color changes (on OSes that support notifications of this ...
Mac is good, not sure about the others).

When we're at that point, we'll probably be having gfx::ICCProfile be a member
of display::Display

[piman, 2016/09/02 23:56:34]

Ok, yes, that makes sense, thanks!
Ok, yes, I think is reasonable, this would probably flow from the WindowTreeHost
implementation (e.g. DesktopWindowTreeHost*), so moving this logic to
WindowTreeHost seems like the right place.

[hubbe, 2016/09/06 20:43:50]

Done.

   delegated_frame_host_->SetCompositor(window_->GetHost()->compositor());
 }