[Webkit-unassigned] [Bug 96403] [chromium] Flings halt immediately on Android content shell

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 11 11:18:39 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=96403





--- Comment #9 from Iain Merrick <husky at chromium.org>  2012-09-11 11:19:02 PST ---
Here's the Android API that we're calling through to:

http://developer.android.com/reference/android/widget/OverScroller.html#fling(int, int, int, int, int, int, int, int)

If we don't set minX/maxX/minY/maxY, the OverScroller object won't know the bounds of the layer being scrolled, so the gesture adapter will just keep calling scrollBy() until the curve finishes. The layer will just ignore any scrollBy() it can't handle.

If we have nested scrollable layers, this does mean that a single fling gesture could spill over into the outer layer. I think we don't want that on Android -- it should stop the fling when the current layer is exhausted, then scroll the outer layer on the *next* fling -- but it's a pretty subtle distinction.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the webkit-unassigned mailing list