chrome: Use base::MessageLoop. (Part 1)

chrome/browser/* will be updated in another CL

BUG=236029
R=sky@chromium.org

Review URL: https://codereview.chromium.org/14314025

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@199547 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 5 insertions, 5 deletions

diff --git a/chrome/test/base/view_event_test_base.cc b/chrome/test/base/view_event_test_base.cc
index 240f63f..d3d9c43 100644
--- a/chrome/test/base/view_event_test_base.cc
+++ b/chrome/test/base/view_event_test_base.cc
@@ -84,7 +84,7 @@ ViewEventTestBase::ViewEventTestBase()
 }
 
 void ViewEventTestBase::Done() {
-  MessageLoop::current()->Quit();
+  base::MessageLoop::current()->Quit();
 
 #if defined(OS_WIN) && !defined(USE_AURA)
   // We need to post a message to tickle the Dispatcher getting called and
@@ -97,7 +97,8 @@ void ViewEventTestBase::Done() {
   // need to quit twice. The second quit does that for us. Finish all
   // pending UI events before posting closure because events it may be
   // executed before UI events are executed.
-  ui_controls::RunClosureAfterAllPendingUIEvents(MessageLoop::QuitClosure());
+  ui_controls::RunClosureAfterAllPendingUIEvents(
+      base::MessageLoop::QuitClosure());
 }
 
 void ViewEventTestBase::SetUp() {
@@ -203,9 +204,8 @@ void ViewEventTestBase::StartMessageLoopAndRunTest() {
 
   // Schedule a task that starts the test. Need to do this as we're going to
   // run the message loop.
-  MessageLoop::current()->PostTask(
-      FROM_HERE,
-      base::Bind(&ViewEventTestBase::DoTestOnMessageLoop, this));
+  base::MessageLoop::current()->PostTask(
+      FROM_HERE, base::Bind(&ViewEventTestBase::DoTestOnMessageLoop, this));
 
   content::RunMessageLoop();
 }