Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(233)

Unified Diff: content/browser/android/content_view_core_impl.cc

Issue 2347373002: Remove velocities parameters from onFlingStartGesture() (Closed)
Patch Set: Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/browser/android/content_view_core_impl.cc
diff --git a/content/browser/android/content_view_core_impl.cc b/content/browser/android/content_view_core_impl.cc
index be027f541172061ac5d0a9d1764e53febe0f8cc1..a7f92639fa22c313db88252bc64615f8ebf06c4a 100644
--- a/content/browser/android/content_view_core_impl.cc
+++ b/content/browser/android/content_view_core_impl.cc
@@ -553,9 +553,7 @@ void ContentViewCoreImpl::OnGestureEventAck(const blink::WebGestureEvent& event,
case WebInputEvent::GestureFlingStart:
if (ack_result == INPUT_EVENT_ACK_STATE_CONSUMED) {
// The view expects the fling velocity in pixels/s.
- Java_ContentViewCore_onFlingStartEventConsumed(
- env, j_obj, event.data.flingStart.velocityX * dpi_scale(),
- event.data.flingStart.velocityY * dpi_scale());
+ Java_ContentViewCore_onFlingStartEventConsumed(env, j_obj);
} else {
// If a scroll ends with a fling, a SCROLL_END event is never sent.
// However, if that fling went unconsumed, we still need to let the

Powered by Google App Engine
This is Rietveld 408576698