Don't use base::MessageLoop::{Quit,QuitClosure} in ui/

ui/events/gesture_detection/gesture_provider_unittest.cc

Index: ui/events/gesture_detection/gesture_provider_unittest.cc
diff --git a/ui/events/gesture_detection/gesture_provider_unittest.cc b/ui/events/gesture_detection/gesture_provider_unittest.cc
index 3cc45f938d5bff6dd143677431979a64996c276f..25611a22386deb2d3acb51389fa9115691ec437e 100644
--- a/ui/events/gesture_detection/gesture_provider_unittest.cc
+++ b/ui/events/gesture_detection/gesture_provider_unittest.cc
@@ -409,7 +409,7 @@ class GestureProviderTest : public testing::Test, public GestureProviderClient {
 
   static void RunTasksAndWait(base::TimeDelta delay) {
     base::MessageLoop::current()->PostDelayedTask(
-        FROM_HERE, base::MessageLoop::QuitClosure(), delay);
+        FROM_HERE, base::MessageLoop::QuitWhenIdleClosure(), delay);
     base::MessageLoop::current()->Run();

[sadrul, 2015/10/09 20:48:25]

This could be a non-static method that uses message_loop_ directly, instead of
MessageLoop::current(), right?

[ki.stfu, 2015/10/09 21:25:37]

Yes in theory, bug I'm not sure base::MessageLoop::current() equals to
message_loop_.
Do you want to change it? 

[ki.stfu, 2015/10/12 19:18:30]

BTW, seems like an unused field at all. I made a new CL to remove it:
https://codereview.chromium.org/1397443005

   }