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 a0af3536a21a22ffcc5e4d6019af07987172b41a..034c8b6295ff3ff9945f2eb52047afb05ab6ea89 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;
+

[ccameron, 2016/09/13 23:34:16]

Ideally, we want to request a full re-raster here. It's not strictly required
for correctness, but "it would be nice". How do we trigger that? TileManager
doesn't seem to have a "wipe out all tiles" method that I found.

[vmpstr, 2016/09/14 23:00:43]

LayerTreeImpl has ReleaseResources/RecreateResources. It does feel a bit
heavyhanded, since it's also going to remove all tilings and scales and things,
but maybe we want that anyway?
https://cs.chromium.org/chromium/src/cc/trees/layer_tree_impl.cc?sq=package:c...

In general though, I feel like if we want to reraster everything, then when we
create a pending tree with a different color space we should be invalidating the
world. Wdyt?

[ccameron, 2016/09/15 07:13:42]

I added a Release+Recreate -- it does indeed feel heavy, but adding a way to
spare the tilings etc is probably not worth the fragility. This should only
happen when moving windows across monitors.

Is the second suggestion to add something to
LayerTreeHostImpl::CreatePendingTree?

+  if (IsActiveTree())
+    layer_tree_host_impl_->SetFullViewportDamage();
+}
+
 SyncedProperty<ScaleGroup>* LayerTreeImpl::page_scale_factor() {
   return page_scale_factor_.get();
 }