android bb: Stop passing --build-dir and --build-output-dir.

These flags are ignored as of r232840 (extract_build.py),
r232782 (zip_build.py), r232641ish (archive_layout_test_results.py).

BUG=314253
R=ilevy@google.com
TBR=ilevy@chromium.org
(who lgtm'd as ilevy@google.com)

Review URL: https://codereview.chromium.org/53153011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232890 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 232890
Add support for rect-based event targeting in views

Views currently only supports point-based event targeting,
meaning that the center point is the only location used
when determining the target of a touch region. This can
lead to a poor experience for touchscreen users because
a touch can overlap many more possible targets than a
mouse cursor and it is difficult to ensure that the center
of the touch region is over the intended target (especially
if that target is small, such as the tab close button).

The goal of this patch is to add support for rect-based
event targeting ("touch fuzzing") by using a heuristic
to determine the most probable target of a rectangular
region.

This heuristic is implemented in
View::GetEventHandlerForRect() by recursively looking for
targets among the descendants of |this| which the
touch region overlaps by at least 60% (and then returning
the one that is closest to the location of the touch). If
no such targets exist, instead return the target that would
have been returned if point-based event targeting were
used with the center point of the touch. The idea behind
this approach is that small targets are more difficult to
touch reliably than large targets, so small targets
should get priority when determining the most probable
target of a touch.

In this patch, all of the overrides of
View::GetEventHandlerForRect() (formerly
View::GetEventHandlerForPoint()) simply call
View::GetEventHandlerForPoint() directly if rect-based
event targeting is to be used. The two exceptions are
NotificationView and AutofillDialogViews::SectionContainer,
for which I have preserved the existing point-based
behavior for the time being (and have added TODOs to
implement rect-based targeting in a follow up patch).

BUG=129794,131208
TEST=ViewTest.GetEventHandlerForRect
R=sky@chromium.org

Review URL: https://codereview.chromium.org/22891016

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@232891 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 232891