Change ordering of Shell event handlers:
crrev.com/14184010 made the DragDropController to be the first handler everytime
a drag starts. That was done under the assumption that once we are in a drag
drop session, no other handler needs to see the event. This assumption turned
out to be false because the MouseCursorEventFilter needs to handle events even
during a drag drop session so that the cursor can move across displays (causing
the bug listed below). Hence, we make the DragDropController the second event
handler while MouseCursorEvedntFilter becomes the first.
BUG=244508
Review URL: https://chromiumcodereview.appspot.com/16463002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204612 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/ash/test/shell_test_api.h b/ash/test/shell_test_api.h
index f36716a..926d1dd 100644
--- a/ash/test/shell_test_api.h
+++ b/ash/test/shell_test_api.h
@@ -19,6 +19,7 @@
class LauncherModel;
namespace internal {
+class DragDropController;
class RootWindowLayoutManager;
class ScreenPositionController;
class SystemGestureEventFilter;
@@ -39,6 +40,7 @@
internal::ScreenPositionController* screen_position_controller();
AshNativeCursorManager* ash_native_cursor_manager();
LauncherModel* launcher_model();
+ internal::DragDropController* drag_drop_controller();
void DisableOutputConfiguratorAnimation();
