cc: Plumb device color space through to rasterization

cc/trees/layer_tree_impl.cc

Index: cc/trees/layer_tree_impl.cc
diff --git a/cc/trees/layer_tree_impl.cc b/cc/trees/layer_tree_impl.cc
index 1376cdf6b5ec4b19aebd7f1168b88c25d401f620..2be96891961d5d31358c01f6394172ef03c4a220 100644
--- a/cc/trees/layer_tree_impl.cc
+++ b/cc/trees/layer_tree_impl.cc
@@ -441,6 +441,7 @@ void LayerTreeImpl::PushPropertiesTo(LayerTreeImpl* target_tree) {
                                             max_page_scale_factor());
   target_tree->SetDeviceScaleFactor(device_scale_factor());
   target_tree->set_painted_device_scale_factor(painted_device_scale_factor());
+  target_tree->SetDeviceColorSpace(device_color_space_);
   target_tree->elastic_overscroll()->PushPendingToActive();
 
   target_tree->pending_page_scale_animation_ =
@@ -850,6 +851,16 @@ void LayerTreeImpl::SetDeviceScaleFactor(float device_scale_factor) {
     layer_tree_host_impl_->SetFullViewportDamage();
 }
 
+void LayerTreeImpl::SetDeviceColorSpace(
+    const gfx::ColorSpace& device_color_space) {
+  if (device_color_space == device_color_space_)
+    return;
+  device_color_space_ = device_color_space;
+
+  if (IsActiveTree())
+    layer_tree_host_impl_->SetFullViewportDamage();

[vmpstr, 2016/09/16 19:01:49]

Do you need this? I think maybe the act of activating a full invalidation will
damage stuff anyway?

[ccameron, 2016/09/16 20:02:38]

Nope, good catch. Removed.

+}
+
 SyncedProperty<ScaleGroup>* LayerTreeImpl::page_scale_factor() {
   return page_scale_factor_.get();
 }