OverscrollGlow for mainThread-{CHROMIUM CHANGES}

content/renderer/render_widget.cc

Index: content/renderer/render_widget.cc
diff --git a/content/renderer/render_widget.cc b/content/renderer/render_widget.cc
index 1aab8b42fc06fd0573f5d5ab6d503e42ea25e637..dbe379f7b74c88f52b0d0303c557b2daa315bcc6 100644
--- a/content/renderer/render_widget.cc
+++ b/content/renderer/render_widget.cc
@@ -2231,6 +2231,25 @@ void RenderWidget::didHandleGestureEvent(
 #endif
 }
 
+void RenderWidget::didOverScrollOnMainThread(
+    const float& unusedDeltaX,
+    const float& unusedDeltaY,
+    const float& accumaltedRootOverScrollX,
+    const float& accumaltedRootOverScrollY,
+    const float& positionX,
+    const float& positionY,
+    const float& velocityX,
+    const float& velocityY) {
+  gfx::Vector2dF unusedDelta(unusedDeltaX, unusedDeltaY);
+  gfx::Vector2dF accumaltedRootOverScroll(accumaltedRootOverScrollX,
+                                          accumaltedRootOverScrollY);
+  gfx::Vector2dF flingVelocity(velocityX, velocityY);
+  gfx::PointF eventPoint(positionX, positionY);
+  Send(new ViewHostMsg_DidOverScrollOnMainThread(routing_id(), unusedDelta,

[jdduke (slow), 2015/04/24 16:57:23]

Can't we just resuse the existing InputHostMsg_DidOverscroll message?
https://code.google.com/p/chromium/codesearch#chromium/src/content/common/inp...

[MuVen, 2015/04/27 09:49:15]

we can call InputHostMsg_DidOverscroll from Render_view_impl itself ?

[jdduke (slow), 2015/04/27 15:00:49]

That's probably fine. To be honest the distribution of methods between RW/RVI
doesn't seem to be very consistent. I guess the argument to put it in
RenderWidget would be that the message gets handled by RenderWidgetHostImp (by
way of the InputRouter), so I have a slight preference for putting the
implementation there.

+                                                 accumaltedRootOverScroll,
+                                                 flingVelocity, eventPoint));
+}
+
 void RenderWidget::StartCompositor() {
   // For widgets that are never visible, we don't need the compositor to run
   // at all.