Prepare CompositorFrameSinkSupport To Be Used By DirectCompositorFrameSink

content/renderer/android/synchronous_compositor_frame_sink.cc

Index: content/renderer/android/synchronous_compositor_frame_sink.cc
diff --git a/content/renderer/android/synchronous_compositor_frame_sink.cc b/content/renderer/android/synchronous_compositor_frame_sink.cc
index 580924cc989b5e194546c89a0f7b9462287c584f..8ec613aa4a0550f4180ebbd9b1512de2bb2cb305 100644
--- a/content/renderer/android/synchronous_compositor_frame_sink.cc
+++ b/content/renderer/android/synchronous_compositor_frame_sink.cc
@@ -168,12 +168,18 @@ bool SynchronousCompositorFrameSink::BindToClient(
                  base::Unretained(this)));
   registry_->RegisterCompositorFrameSink(routing_id_, this);
 
+  const bool root_submits_to_display_compositor = true;

[danakj, 2017/02/14 16:54:01]

We were talking about names with fsamuel the other day and he mentioned that
this concept of "offscreen" really means "not-root". I wonder if that applies
here too.. in that children also submit frames to a display compositor too
right? They are just not the root of the display compositor. So I wonder if
these should be named in those terms (root vs child)?

+  const bool child_submits_to_display_compositor = false;
+  const bool handles_frame_sink_id_invalidation = true;
+  const bool needs_sync_points = true;
   root_support_.reset(new cc::CompositorFrameSinkSupport(
       this, surface_manager_.get(), kRootFrameSinkId,
-      true /* submits_to_display_compositor */));
+      root_submits_to_display_compositor, handles_frame_sink_id_invalidation,
+      needs_sync_points));
   child_support_.reset(new cc::CompositorFrameSinkSupport(
       this, surface_manager_.get(), kChildFrameSinkId,
-      false /* submits_to_display_compositor */));
+      child_submits_to_display_compositor, handles_frame_sink_id_invalidation,
+      needs_sync_points));
 
   cc::RendererSettings software_renderer_settings;