Separate SwipeRefreshHandler and ContentViewCore

content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java

Index: content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java b/content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java
index 8717b8384fe5ee05835cea8ff01d438a89c7dc8c..f89617cb55f46134bb4be8a54b05bce3eb2d9edc 100644
--- a/content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java
+++ b/content/public/android/java/src/org/chromium/content/browser/OverscrollRefreshHandler.java
@@ -37,4 +37,10 @@ public interface OverscrollRefreshHandler {
      *                If disabled, the effect should deactive itself apropriately.
      */
     public void setEnabled(boolean enabled);
+
+    /**
+     * Gets pointer to the native OverscrollRefreshHandler instance associated
+     * with the Java instance.
+     */
+    public long getNativePtr();

[Ted C, 2016/11/29 00:06:08]

public is implied on interfaces, so this method (nor any of the others in the
file) need it.

In general, we want to ever expose a native pointer outside of a class.  You
should prefer passing down a java obj and have the native side talk to it via
the normal JNI boundary.

For this class, could you just add @CalledByNative to all other methods in the
interface and then get rid of your
chrome/browser/android/swipe_refresh_handler.[cc|h] files?  Those seem to only
act as the jni bouncer.

 }