|
|
The way this is going to work is as follows:
* The OverscrollController receives events as they are sent to the
renderer and, the ACKs for the interesting events (i.e. gesture, wheel).
* It decides whether to initiate an overscroll gesture, and notifies the
OverscrollControllerDelegate appropriately for each overscroll state update.
* The delegate takes care of updating the display during this overscroll
gesture (and resetting the display when it is cancelled).
* The controller recognizes whether the overscroll gesture was complete or not
based on some heuristic on the amount of scroll. The delegate decides what
to do with the overscroll gesture.
This CL implementes these steps (with relevant tests). But it creates the controller
only for the tests. Subsequent CLs are going to:
* Turn RenderWidgetHostViewAura into a delegate for overscroll-controller so
that it receives the updates for overscroll gesture.
* Add a flag that can be used to turn on the overscroll controller.
* Update display from RenderWidgetHostViewAura (or move the display to another
layer)
BUG=160668
Review URL: https://codereview.chromium.org/11293238
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168102 0039d316-1c4b-4281-b951-d872f2087c98
|
