cc: Glue LTHI and Scheduler changes for checker-imaging.

cc/trees/proxy_impl.cc

Index: cc/trees/proxy_impl.cc
diff --git a/cc/trees/proxy_impl.cc b/cc/trees/proxy_impl.cc
index 7c2cb9fb26e060c5caf2f4c3a4d8887ec04d7ae1..89c72da632a75c009137ec943c91d32bb7b8a16b 100644
--- a/cc/trees/proxy_impl.cc
+++ b/cc/trees/proxy_impl.cc
@@ -434,9 +434,7 @@ void ProxyImpl::OnDrawForCompositorFrameSink(bool resourceless_software_draw) {
 
 void ProxyImpl::NeedsImplSideInvalidation() {
   DCHECK(IsImplThread());
-  // TODO(khushalsagar): Plumb this to the scheduler when
-  // https://codereview.chromium.org/2659123004/ lands. See crbug.com/686267.
-  NOTIMPLEMENTED();
+  scheduler_->SetNeedsImplSideInvalidation();
 }
 
 void ProxyImpl::WillBeginImplFrame(const BeginFrameArgs& args) {
@@ -467,6 +465,7 @@ void ProxyImpl::ScheduledActionSendBeginMainFrame(const BeginFrameArgs& args) {
   MainThreadTaskRunner()->PostTask(
       FROM_HERE, base::Bind(&ProxyMain::BeginMainFrame, proxy_main_weak_ptr_,
                             base::Passed(&begin_main_frame_state)));
+  layer_tree_host_impl_->DidSendBeginMainFrameForTesting();

[vmpstr, 2017/02/27 21:16:57]

I don't think this is correct. We shouldn't be calling "for testing" functions
in non-for testing code.

[Khushal, 2017/02/27 21:43:01]

We kinda do that with MainFrameWillHappenForTesting in the proxies, but it does
start with test code.
Do you think I should just not bother making it ForTesting then?

   devtools_instrumentation::DidRequestMainThreadFrame(layer_tree_host_id_);
 }
 
@@ -556,7 +555,9 @@ void ProxyImpl::ScheduledActionInvalidateCompositorFrameSink() {
 }
 
 void ProxyImpl::ScheduledActionPerformImplSideInvalidation() {
-  NOTIMPLEMENTED();
+  TRACE_EVENT0("cc", "ProxyImpl::ScheduledActionPerformImplSideInvalidation");
+  DCHECK(IsImplThread());
+  layer_tree_host_impl_->InvalidateContentOnImplSide();
 }
 
 void ProxyImpl::SendBeginMainFrameNotExpectedSoon() {