Add/remove surface references via MojoCompositorFrameSink.

services/ui/surfaces/gpu_compositor_frame_sink.cc

Index: services/ui/surfaces/gpu_compositor_frame_sink.cc
diff --git a/services/ui/surfaces/gpu_compositor_frame_sink.cc b/services/ui/surfaces/gpu_compositor_frame_sink.cc
index b27e881e0f3bed73c1a9ccb77e535803ec734844..bc35f309985ed936c0590a6d2cec8de58b889830 100644
--- a/services/ui/surfaces/gpu_compositor_frame_sink.cc
+++ b/services/ui/surfaces/gpu_compositor_frame_sink.cc
@@ -97,6 +97,18 @@ void GpuCompositorFrameSink::SubmitCompositorFrame(
   }
 }
 
+void GpuCompositorFrameSink::AddSurfaceReferences(
+    const std::vector<cc::SurfaceReference>& references) {
+  for (auto& ref : references)
+    display_compositor_->AddSurfaceReference(ref);

[Fady Samuel, 2016/12/04 23:30:12]

I'd love to see this added to CompositorFrameSinkSupport. I think we might need
a display compositor support to make that happen.

If we do that then we can start looking into transitioning ui::Compositor away
from SurfaceSequences *I think*.

[kylechar, 2016/12/05 20:26:45]

CompositorFrameSinkSupport doesn't have access to DisplayCompositor, is that
what you mean?

+}
+
+void GpuCompositorFrameSink::RemoveSurfaceReferences(
+    const std::vector<cc::SurfaceReference>& references) {
+  for (auto& ref : references)
+    display_compositor_->RemoveSurfaceReference(ref);
+}
+
 void GpuCompositorFrameSink::DidReceiveCompositorFrameAck() {
   if (!client_)
     return;