| commit | 7a4fa927acf418ad17ed93a0ccdaf83f3b7dfe27 | |
| author | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sat, 12 Jul 2014 06:18:21 +0000 (12 06:18 +0000) | ||
| committer | sadrul@chromium.org <sadrul@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sat, 12 Jul 2014 06:18:21 +0000 (12 06:18 +0000) | ||
| tree | 5287b93d7b5cf51eace8077a5b6754082dee99af | treesnapshot (tar.gz zip) |
| parent | a5d20a27ea5dc48d3e80726b596c248be8970251 | commitdiff |
aura: Do not synthesize a mouse-move event during a drag.
Synthesizing a mouse-move event during a drag can cause an inconsistent sequence
of events to be dispatched (e.g. pressed, dragged, dragged, moved, dragged ...
released). So do not synthesize mouse-move events when a drag is in progress. The
alternate is to synthesize mouse-dragged event instead of a mouse-move event, but
in multi-display/multi-host setting, the wrong dispatcher may end up synthesizing
the event. So avoid doing that.
BUG=389424, 369247, 366096
R=oshima@chromium.org
Review URL: https://codereview.chromium.org/387863003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282805 0039d316-1c4b-4281-b951-d872f2087c98
Synthesizing a mouse-move event during a drag can cause an inconsistent sequence
of events to be dispatched (e.g. pressed, dragged, dragged, moved, dragged ...
released). So do not synthesize mouse-move events when a drag is in progress. The
alternate is to synthesize mouse-dragged event instead of a mouse-move event, but
in multi-display/multi-host setting, the wrong dispatcher may end up synthesizing
the event. So avoid doing that.
BUG=389424, 369247, 366096
R=oshima@chromium.org
Review URL: https://codereview.chromium.org/387863003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282805 0039d316-1c4b-4281-b951-d872f2087c98
| ui/aura/window_event_dispatcher.cc | diffblobblamehistory | |
| ui/aura/window_event_dispatcher_unittest.cc | diffblobblamehistory |