Revert of Avoid two targeting phases in aura client-lib and EventProcessor.

Revert of Avoid two targeting phases in aura client-lib and EventProcessor. (patchset #9 id:220001 of https://codereview.chromium.org/2681613002/ )

Reason for revert:
This patch broke window resizing (specifically when making windows bigger and when mouse event location is outside the window bounds for certain distance) in mash. Will fix this before relanding.

Original issue's description:
> Avoid two targeting phases in aura client-lib and EventProcessor.
> 
> 1. Client-lib now skips the step where it converted the event location from
> target window's coordinate system to root window's coordinate system; and
> sets the target window received from mus-ws to be the target for that event.
> 
> 2. Added two virtual functions in EventProcessor responsible for getting the
> window with the right targeter (either root window or the farthest ancestor
> with a targeter set) and for getting the default targeter (WindowTargeter)
> respectively.
> 
> 3. WindowEventDispatcher now is responsible for finding the right target and
> doing the conversion between their coordinate systems.
> 
> 4. WindowTreeHost only sets a targeter for the root window in non-mus mode 
> so that we don't end up walking all the way up to the root window just to use
> the default event targeter.
> 
> This also solves the bug where we were using DIP for conversion in the
> client-lib but event location was still in pixels at that time.
> 
> BUG=687700
> TEST=aura_unittests
>      manual (--force-device-scale-factor=2)
> 
> Review-Url: https://codereview.chromium.org/2681613002
> Cr-Commit-Position: refs/heads/master@{#452393}
> Committed: https://chromium.googlesource.com/chromium/src/+/6b3d9805494f966193ad47181d39544d541e79f2

TBR=sadrul@chromium.org,sky@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=687700
Review-Url: https://codereview.chromium.org/2715743005
Cr-Commit-Position: refs/heads/master@{#452679}
Committed: https://chromium.googlesource.com/chromium/src/+/4e8acf39f19aead0fff12ac584988a29571db65c

[riajiang, 2017-02-23 23:57:38]

The CQ bit was checked by riajiang@chromium.org

[riajiang, 2017-02-23 23:57:39]

Created Revert of Avoid two targeting phases in aura client-lib and
EventProcessor.

[commit-bot: I haz the power, 2017-02-23 23:58:33]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-23 23:59:56]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487894258929210, "parent_rev":
"bdfe69d301b8826665a213a553647e26f3b198c1", "commit_rev":
"4e8acf39f19aead0fff12ac584988a29571db65c"}

[commit-bot: I haz the power, 2017-02-24 00:00:33]

Description was changed from

==========
Revert of Avoid two targeting phases in aura client-lib and EventProcessor.
(patchset #9 id:220001 of https://codereview.chromium.org/2681613002/ )

Reason for revert:
This patch broke window resizing (specifically when making windows bigger and
when mouse event location is outside the window bounds for certain distance) in
mash. Will fix this before relanding.

Original issue's description:
> Avoid two targeting phases in aura client-lib and EventProcessor.
> 
> 1. Client-lib now skips the step where it converted the event location from
> target window's coordinate system to root window's coordinate system; and
> sets the target window received from mus-ws to be the target for that event.
> 
> 2. Added two virtual functions in EventProcessor responsible for getting the
> window with the right targeter (either root window or the farthest ancestor
> with a targeter set) and for getting the default targeter (WindowTargeter)
> respectively.
> 
> 3. WindowEventDispatcher now is responsible for finding the right target and
> doing the conversion between their coordinate systems.
> 
> 4. WindowTreeHost only sets a targeter for the root window in non-mus mode 
> so that we don't end up walking all the way up to the root window just to use
> the default event targeter.
> 
> This also solves the bug where we were using DIP for conversion in the
> client-lib but event location was still in pixels at that time.
> 
> BUG=687700
> TEST=aura_unittests
>      manual (--force-device-scale-factor=2)
> 
> Review-Url: https://codereview.chromium.org/2681613002
> Cr-Commit-Position: refs/heads/master@{#452393}
> Committed:
https://chromium.googlesource.com/chromium/src/+/6b3d9805494f966193ad47181d39...

TBR=sadrul@chromium.org,sky@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=687700
==========

to

==========
Revert of Avoid two targeting phases in aura client-lib and EventProcessor.
(patchset #9 id:220001 of https://codereview.chromium.org/2681613002/ )

Reason for revert:
This patch broke window resizing (specifically when making windows bigger and
when mouse event location is outside the window bounds for certain distance) in
mash. Will fix this before relanding.

Original issue's description:
> Avoid two targeting phases in aura client-lib and EventProcessor.
> 
> 1. Client-lib now skips the step where it converted the event location from
> target window's coordinate system to root window's coordinate system; and
> sets the target window received from mus-ws to be the target for that event.
> 
> 2. Added two virtual functions in EventProcessor responsible for getting the
> window with the right targeter (either root window or the farthest ancestor
> with a targeter set) and for getting the default targeter (WindowTargeter)
> respectively.
> 
> 3. WindowEventDispatcher now is responsible for finding the right target and
> doing the conversion between their coordinate systems.
> 
> 4. WindowTreeHost only sets a targeter for the root window in non-mus mode 
> so that we don't end up walking all the way up to the root window just to use
> the default event targeter.
> 
> This also solves the bug where we were using DIP for conversion in the
> client-lib but event location was still in pixels at that time.
> 
> BUG=687700
> TEST=aura_unittests
>      manual (--force-device-scale-factor=2)
> 
> Review-Url: https://codereview.chromium.org/2681613002
> Cr-Commit-Position: refs/heads/master@{#452393}
> Committed:
https://chromium.googlesource.com/chromium/src/+/6b3d9805494f966193ad47181d39...

TBR=sadrul@chromium.org,sky@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=687700

Review-Url: https://codereview.chromium.org/2715743005
Cr-Commit-Position: refs/heads/master@{#452679}
Committed:
https://chromium.googlesource.com/chromium/src/+/4e8acf39f19aead0fff12ac58498...
==========

[commit-bot: I haz the power, 2017-02-24 00:00:35]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/4e8acf39f19aead0fff12ac58498...