[Webkit-unassigned] [Bug 95322] [chromium] Fix double call to scrollBegin() when handling scroll gesture

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Sep 5 10:53:32 PDT 2012


--- Comment #12 from Iain Merrick <husky at chromium.org>  2012-09-05 10:53:45 PST ---
(In reply to comment #11)
> This doesn't look right.  Keep in mind we have 2 kinds of flings - "gesture" flings and "wheel pad" flings.  The former is what Chrome on android has.  The latter - which is what this code implements - works like OS X fling by generating a sequence of synthetic wheel events.
> It looks like you've just deleted the code for the second kind of fling completely.  That's definitely not the right fix!

It did seem a bit strange, yes. :) Chrome for Android is hitting that code path, though, and it sounds like maybe it shouldn't -- I'll take a closer look.

> I think what you really want to do is for wheel fling type scrolls send a matching scrollEnd() to the scrollBegin() when the fling starts.

np, will do

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