Ignore "range" parameter in Android FlingAnimator

Ignore "range" parameter in Android FlingAnimator

WebKit is passing an empty range, which means flings are always
immediately halted on Android. This patch ignores the parameter
and just uses INT_MIN / INT_MAX for the range. This fixes fling
gestures in the Android content shell.

Also simplified code by calling an overloaded Java method with
fewer parameters (we were just passing 0 for the extra "overfling
range" parameters, and they have no effect anyway unless we hit
the max scrolling range, which this patch prevents).

Other platforms don't need this parameter so we'll probably
just remove it from the WebKit API. See discussion on WebKit
bug: http://webkit.org/b/96403

BUG=None
TEST=Manual


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=156416

[jamesr, 2012-09-12 18:25:41]

This is fine for now, but it looks like you really do need the actual fling
parameters to set up the correct curve.

lgtm

[commit-bot: I haz the power, 2012-09-12 19:41:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/husky@chromium.org/10913218/1

[commit-bot: I haz the power, 2012-09-12 23:23:35]

Change committed as 156416