Add gesture target fuzzing to views

ui/views/view_constants.h

Index: ui/views/view_constants.h
diff --git a/ui/views/view_constants.h b/ui/views/view_constants.h
index 2b0171f19db780faeb0bd784708f472c08332d37..3d495c20fa92a1caf07b606cb1a15a170d6d45e3 100644
--- a/ui/views/view_constants.h
+++ b/ui/views/view_constants.h
@@ -22,6 +22,11 @@ VIEWS_EXPORT extern const int kAutoscrollRowTimerMS;
 // the item, otherwise it is on the item.
 VIEWS_EXPORT extern const int kDropBetweenPixels;
 
+// A view will only be considered a candidate for touch fuzzing if the touch
+// region covers at least |kFuzzingOverlapPercentage| percent of the area of
+// the view's bounding rectangle.
+VIEWS_EXPORT extern const float kFuzzingOverlapPercentage;

[rjkroege, 2012/07/16 23:35:48]

So... If we have a really huge button, can we fail to hit it?

[tdanderson, 2012/07/17 19:07:07]

This is a good question, and I should have mentioned this in the CL description.
The benefit of fuzzing is for small targets only, and by "small targets" I mean
targets that your finger can cover by at least 70%. The algorithm first tries to
dispatch the tap event to the closest small target; if there are none or if the
target doesn't handle the tap, then the event is dispatched to the center of the
touch region (which is what the code did originally). 

So in the case of a large view such as a tab, assuming that the user's finger
did not sufficiently cover the tab close button, there should be no problem
hitting it because it is large enough for the user to touch without the help of
fuzzing (i.e., it is easy to touch a tab so that the center of the touch region
is contained within the tab).

+
 }  // namespace views
 
 #endif  // UI_VIEWS_VIEW_CONSTANTS_H_