Fixing flaky overscroll and touch exploration mode browser tests.

chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc

Index: chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc
diff --git a/chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc b/chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc
index 8ede979dbe0449147ecdc7df7ce726eb16431bb0..67aa3ba87c37fc7bdb20c8bc5c5cc2316fbfd265 100644
--- a/chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc
+++ b/chrome/browser/chromeos/accessibility/touch_exploration_controller_browsertest.cc
@@ -34,7 +34,7 @@ private:
   DISALLOW_COPY_AND_ASSIGN(TouchExplorationTest);
 };
 
-IN_PROC_BROWSER_TEST_F(TouchExplorationTest, PRE_ToggleOnOff) {
+//IN_PROC_BROWSER_TEST_F(TouchExplorationTest, PRE_ToggleOnOff) {
   // TODO (mfomitchev): If the test is run by itself, there is a resize at the
   //  very beginning. An in-progress resize creates a "resize lock" in
   // RenderWidgetHostViewAura, which calls
@@ -42,7 +42,7 @@ IN_PROC_BROWSER_TEST_F(TouchExplorationTest, PRE_ToggleOnOff) {
   // coming through. Adding a PRE_ test ensures the resize completes before the
   // actual test is executed. sadrul@ says the resize shouldn't be even
   // happening, so this needs to be looked at further.
-}
+//}
 
 // This test turns the touch exploration mode on/off and confirms that events
 // get rewritten when the touch exploration mode is on, and aren't affected