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

chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc

Index: chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc
diff --git a/chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc b/chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc
index 17ea9735efedf6bab9b1adf4701cb9b46e79fc6b..da3db669ef5566466f5128210e5c3ea47d062e88 100644
--- a/chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc
+++ b/chrome/browser/ui/gtk/infobars/after_translate_infobar_gtk.cc
@@ -97,7 +97,7 @@ void AfterTranslateInfoBar::OnOriginalLanguageModified(GtkWidget* sender) {
   // Setting the language will lead to a new translation that is going to close
   // the infobar.  This is not OK to do this from the signal handler, so we'll
   // defer it.
-  MessageLoop::current()->PostTask(
+  base::MessageLoop::current()->PostTask(
       FROM_HERE,
       base::Bind(&AfterTranslateInfoBar::SetOriginalLanguage,
                  weak_factory_.GetWeakPtr(),
@@ -110,7 +110,7 @@ void AfterTranslateInfoBar::OnTargetLanguageModified(GtkWidget* sender) {
     return;
 
   // See comment in OnOriginalLanguageModified on why we use a task.
-  MessageLoop::current()->PostTask(
+  base::MessageLoop::current()->PostTask(
       FROM_HERE,
       base::Bind(&AfterTranslateInfoBar::SetTargetLanguage,
                  weak_factory_.GetWeakPtr(),