| commit | 61a1c4b9d3dfb560260366304e44d4fd7bc634db | |
| author | mohsen@chromium.org <mohsen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Wed, 9 Oct 2013 23:47:50 +0000 (9 23:47 +0000) | ||
| committer | mohsen@chromium.org <mohsen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Wed, 9 Oct 2013 23:47:50 +0000 (9 23:47 +0000) | ||
| tree | 233176e53cf13856d187b1b739196bd19422fa4b | treesnapshot (tar.gz zip) |
| parent | ae56dd8a59018b7ed0af0757c0c8b385a25795a8 | commitdiff |
Do not send mouse-move when target is destroyed due to synthesized mouse-exit in RootWindow
When a RootWindow is going to dispatch a mouse-move to a child, if the
target is different than the current mouse_moved_handler_, it sends a
synthesized mouse-exit to to mouse_moved_handler_. The target might be
destroyed because of this mouse-exit. If that's the case, the original
mouse-move should not be sent to the destroyed target.
BUG=304276
Review URL: https://codereview.chromium.org/26499003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227835 0039d316-1c4b-4281-b951-d872f2087c98
When a RootWindow is going to dispatch a mouse-move to a child, if the
target is different than the current mouse_moved_handler_, it sends a
synthesized mouse-exit to to mouse_moved_handler_. The target might be
destroyed because of this mouse-exit. If that's the case, the original
mouse-move should not be sent to the destroyed target.
BUG=304276
Review URL: https://codereview.chromium.org/26499003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@227835 0039d316-1c4b-4281-b951-d872f2087c98
| ui/aura/root_window.cc | diffblobblamehistory | |
| ui/aura/root_window_unittest.cc | diffblobblamehistory |