OverscrollGlow for mainThread-{BLINK CHANGES}

Source/web/WebViewImpl.cpp

Index: Source/web/WebViewImpl.cpp
diff --git a/Source/web/WebViewImpl.cpp b/Source/web/WebViewImpl.cpp
index 870913bbd6e4a9e2bfee1a1f3deac1a83680c753..e3cec21323d309818d2b7570dee52ce354d2e260 100644
--- a/Source/web/WebViewImpl.cpp
+++ b/Source/web/WebViewImpl.cpp
@@ -727,6 +727,13 @@ bool WebViewImpl::handleGestureEvent(const WebGestureEvent& event)
         // Perhaps we could simplify things by rewriting scroll handling to work inner frame
         // out, and then unify with other gesture events.
         eventSwallowed = mainFrameImpl()->frame()->eventHandler().handleGestureScrollEvent(platformEvent);
+        {
+            FloatPoint unusedDelta = mainFrameImpl()->frame()->eventHandler().unusedDelta();
+            if (unusedDelta != FloatPoint() && (event.type == WebInputEvent::GestureScrollUpdate)) {
+                FloatPoint accumaltedRootOverScroll = mainFrameImpl()->frame()->eventHandler().accumulatedRootOverScroll();
+                m_client->didOverScrollOnMainThread(unusedDelta.x(), unusedDelta.y(), accumaltedRootOverScroll.x(), accumaltedRootOverScroll.y(), platformEvent.position().x(), platformEvent.position().y(), platformEvent.velocityX(), platformEvent.velocityY());

[aelias_OOO_until_Jul13, 2015/05/01 04:45:04]

Can this be called directly from handleGestureScrollUpdate, so that the logic
isn't split across two gesture handling methods and shared implicitly using
member variables?  (It's fine if it needs to pass through a new WebViewImpl
plumbing method to do that.)

[MuVen, 2015/05/04 09:04:18]

Done.

+            }
+        }
         m_client->didHandleGestureEvent(event, eventCancelled);
         return eventSwallowed;
     case WebInputEvent::GesturePinchBegin: