color: Use ICCProfile from display::Display instead of FromBestMonitor

cc/surfaces/surface_aggregator.cc

Index: cc/surfaces/surface_aggregator.cc
diff --git a/cc/surfaces/surface_aggregator.cc b/cc/surfaces/surface_aggregator.cc
index a17440557d38cdee838ec0c3d3218fc3454b6a03..012779976ee889c147613ba436c1442cc7652490 100644
--- a/cc/surfaces/surface_aggregator.cc
+++ b/cc/surfaces/surface_aggregator.cc
@@ -938,8 +938,12 @@ void SurfaceAggregator::SetFullDamageForSurface(const SurfaceId& surface_id) {
 void SurfaceAggregator::SetOutputColorSpace(
     const gfx::ColorSpace& blending_color_space,
     const gfx::ColorSpace& output_color_space) {
-  blending_color_space_ = blending_color_space;
-  output_color_space_ = output_color_space;
+  blending_color_space_ = blending_color_space.IsValid()

[hubbe, 2017/06/23 21:31:52]

Can we just DCHECK() instead?

[ccameron, 2017/06/23 22:44:10]

There's the question: "Suppose we can't parse a display's ICC profile. At what
point do we compensate for that?".

For the moment, this is the choke point that all paths go through.

Once we get a bit more cleanup in place, I'd like to add DCHECKs here, and
remove the validation. But first we'll need to clean up the platform-specific
color profile code.

+                              ? blending_color_space
+                              : gfx::ColorSpace::CreateSRGB();
+  output_color_space_ = output_color_space.IsValid()
+                            ? output_color_space
+                            : gfx::ColorSpace::CreateSRGB();
 }
 
 }  // namespace cc