diff options
author | tdanderson@chromium.org <tdanderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-05 22:28:50 +0000 |
---|---|---|
committer | tdanderson@chromium.org <tdanderson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-05 22:28:50 +0000 |
commit | 11f57949d5726af24f66cdec331347afe14bfc8e (patch) | |
tree | 6361fd6140dd6f3e9d94108477163a83901afcc5 /ui/file_manager | |
parent | a58554aaf521e3c2f61a86f7b9bf34d2a5204525 (diff) | |
download | chromium_src-11f57949d5726af24f66cdec331347afe14bfc8e.zip chromium_src-11f57949d5726af24f66cdec331347afe14bfc8e.tar.gz chromium_src-11f57949d5726af24f66cdec331347afe14bfc8e.tar.bz2 |
Do not call into EventTargeter methods from ViewTargeter
Now that hit-testing for views (crbug.com/388838) and
event-targeting for views (crbug.com/391845) use
ViewTargeterDelegate to define custom behaviour for
these operations (instead of the now-obsolete
approach of subclassing ViewTargeter itself), we
should not be calling into EventTargeter for this
purpose. Changes in this CL:
* Finding the target of a scroll event is now
performed correctly by using the logic in
ViewTargeterDelegate and its overrides.
* The dead code
ViewTargeter::SubtreeCanAcceptEvent(),
ViewTargeter::EventLocationInsideBounds(),
and ViewTargeter::BoundsForEvent() have been
removed along with their corresponding tests.
* The class-level documentation for ViewTargeter
and ViewTargeterDelegate has been updated
to clarify the purpose of these classes.
BUG=395387,370579
TEST=ViewTargeterTest.*
Review URL: https://codereview.chromium.org/426443002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287620 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/file_manager')
0 files changed, 0 insertions, 0 deletions