RESOLVED FIXED 96183
[chromium] Add GestureTapCancel WebGestureEvent type 
https://bugs.webkit.org/show_bug.cgi?id=96183
Summary [chromium] Add GestureTapCancel WebGestureEvent type
Rick Byers
Reported 2012-09-08 08:01:23 PDT
The first step for bug 96060 is to add a new unused gesture type to the chromium layer. For now we just ignore any such gestures, so that we can update chromium to send them without breaking anything. Then we can update WebCore to rely on them.
Attachments
Patch (4.13 KB, patch)
2012-09-08 11:13 PDT, Rick Byers 		no flags
DetailsFormatted DiffDiff
Patch (6.54 KB, patch)
2012-09-08 13:37 PDT, Rick Byers 		no flags
DetailsFormatted DiffDiff
Patch (5.79 KB, patch)
2012-09-08 19:03 PDT, Rick Byers 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
Rick Byers
Comment 1 2012-09-08 11:13:08 PDT
Created attachment 162962 [details] Patch
WebKit Review Bot
Comment 2 2012-09-08 11:16:06 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
WebKit Review Bot
Comment 3 2012-09-08 11:20:23 PDT
Comment on attachment 162962 [details] Patch Attachment 162962 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/13789590
Rick Byers
Comment 4 2012-09-08 13:37:29 PDT
Created attachment 162966 [details] Patch
Rick Byers
Comment 5 2012-09-08 19:03:37 PDT
Created attachment 162973 [details] Patch
Adam Barth
Comment 6 2012-09-10 12:51:44 PDT
Comment on attachment 162973 [details] Patch ok
WebKit Review Bot
Comment 7 2012-09-10 13:09:24 PDT
Comment on attachment 162973 [details] Patch Clearing flags on attachment: 162973 Committed r128093: <http://trac.webkit.org/changeset/128093>
WebKit Review Bot
Comment 8 2012-09-10 13:09:27 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.