Summary: | [chromium] Gesture recognizer fires taptype only every other touch down/up sequence | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Robert Kroeger <rjkroege> | ||||||
Component: | UI Events | Assignee: | Robert Kroeger <rjkroege> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | abarth, rjkroege, varunjain, webkit.review.bot | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Attachments: |
|
Description
Robert Kroeger
2011-09-19 10:02:15 PDT
Created attachment 107876 [details]
Patch
Hi Adam, Could you have at this small bug fix for the GestureRecognizer please? Thanks. Comment on attachment 107876 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=107876&action=review > Source/WebCore/ChangeLog:9 > + outgoing edges in the recognizer state machine. Thsi change simplifies the logic Thsi => This > Source/WebCore/platform/chromium/GestureRecognizerChromium.cpp:39 > +static const double maximumSecondsBetweenDoubleClick = .7; Maybe use a leading 0 to be consistent with the declarations above? I can fix this. New patch attached rsn. Created attachment 107891 [details]
Patch
Comment on attachment 107891 [details] Patch Clearing flags on attachment: 107891 Committed r95452: <http://trac.webkit.org/changeset/95452> All reviewed patches have been landed. Closing bug. |