Use scroll-boundary-behavior to control overscroll-refresh/glow on android.

ui/events/blink/did_overscroll_params.h

Index: ui/events/blink/did_overscroll_params.h
diff --git a/ui/events/blink/did_overscroll_params.h b/ui/events/blink/did_overscroll_params.h
index 46eeb15d1a57717184559cdc26d1d34b577e8a9d..97673812da656e201013d5fcf65d7b74f9f48e5c 100644
--- a/ui/events/blink/did_overscroll_params.h
+++ b/ui/events/blink/did_overscroll_params.h
@@ -5,6 +5,7 @@
 #ifndef UI_EVENTS_BLINK_DID_OVERSCROLL_PARAMS_H_
 #define UI_EVENTS_BLINK_DID_OVERSCROLL_PARAMS_H_
 
+#include "cc/input/scroll_boundary_behavior.h"
 #include "ui/gfx/geometry/point_f.h"
 #include "ui/gfx/geometry/vector2d_f.h"
 
@@ -13,10 +14,14 @@ namespace ui {
 struct DidOverscrollParams {
   DidOverscrollParams();
   ~DidOverscrollParams();
+  void ClearX();
+  void ClearY();
+
   gfx::Vector2dF accumulated_overscroll;
   gfx::Vector2dF latest_overscroll_delta;
   gfx::Vector2dF current_fling_velocity;
   gfx::PointF causal_event_viewport_point;
+  cc::ScrollBoundaryBehavior scroll_boundary_behavior;

[majidvp, 2017/05/18 15:26:10]

I wonder if there is a preference to use the WebScrollBoundaryBehavior instead?
Perhaps best to consult
one of the OWNERs e.g., @dtapuska to see if there is a guideline.

[sunyunjia, 2017/05/19 20:14:24]

Dave said that the cc value is fine in this struct

 };
 
 }  // namespace ui