Add initial CC support for scroll-blocks-on

content/renderer/input/input_handler_proxy.cc

Index: content/renderer/input/input_handler_proxy.cc
diff --git a/content/renderer/input/input_handler_proxy.cc b/content/renderer/input/input_handler_proxy.cc
index 7f5c6925da2361a62bd8f62b956e1a3015a8a9b4..aedc326cd07477680a5e25af3b5389a3034aa6a1 100644
--- a/content/renderer/input/input_handler_proxy.cc
+++ b/content/renderer/input/input_handler_proxy.cc
@@ -558,9 +558,11 @@ InputHandlerProxy::EventDisposition InputHandlerProxy::HandleTouchStart(
   for (size_t i = 0; i < touch_event.touchesLength; ++i) {
     if (touch_event.touches[i].state != WebTouchPoint::StatePressed)
       continue;
-    if (input_handler_->HaveTouchEventHandlersAt(
+    if (input_handler_->DoTouchEventsBlockScrollAt(
             gfx::Point(touch_event.touches[i].position.x,
                        touch_event.touches[i].position.y))) {
+      // TODO(rbyers): We should consider still sending the touch events to
+      // main asynchronously (crbug.com/347272).

[jdduke (slow), 2015/02/03 16:43:35]

Might be nice to have a more specific bug for this behavior, but not necessary.

[Rick Byers, 2015/02/05 04:35:53]

Yeah, good idea.  At some point we might want to weigh the cost/benefit tradeoff
of doing that - good to have one bug to track the debate.  Done.

       return DID_NOT_HANDLE;
     }
   }