You need to
before you can comment on or make changes to this bug.
Once https://bugs.webkit.org/show_bug.cgi?id=85101 lands, there will be some unnecessary code I had previously landed for tap target fuzzing that can be removed:
https://bugs.webkit.org/show_bug.cgi?id=84053 - WebGestureEvent will no longer need to store gammaX and gammaY. Now we will only need the touch center along with deltaX and deltaY (which represent the touch radii). These values define a rectangular touch region having width 2*deltaX and height 2*deltaY.
https://bugs.webkit.org/show_bug.cgi?id=85296 - Originally I had planned on passing in a pre-targeted node to EventHandler::handleGestureTap. But instead, WK85101 allows chromium to use the existing touch_adjustment code to determine the best target given a rectangular touch region.
Created an attachment (id=141498) [details]
Please wait for approval from firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com or firstname.lastname@example.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
(From update of attachment 141498 [details])
Clearing flags on attachment: 141498
Committed r117098: <http://trac.webkit.org/changeset/117098>
All reviewed patches have been landed. Closing bug.