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

chrome/browser/autofill/risk/fingerprint_browsertest.cc

Index: chrome/browser/autofill/risk/fingerprint_browsertest.cc
diff --git a/chrome/browser/autofill/risk/fingerprint_browsertest.cc b/chrome/browser/autofill/risk/fingerprint_browsertest.cc
index f74bcedfa9b45ca4763d5e2a2c22c6ed4f86cf8f..6d7b4e4e20a6e8dc8c568d05563f7e6096fd6812 100644
--- a/chrome/browser/autofill/risk/fingerprint_browsertest.cc
+++ b/chrome/browser/autofill/risk/fingerprint_browsertest.cc
@@ -40,7 +40,7 @@ class AutofillRiskFingerprintTest : public InProcessBrowserTest {
         kScreenBounds(0, 0, 101, 71),
         kAvailableScreenBounds(0, 11, 101, 60),
         kUnavailableScreenBounds(0, 0, 101, 11),
-        message_loop_(MessageLoop::TYPE_UI) {}
+        message_loop_(base::MessageLoop::TYPE_UI) {}
 
   void GetFingerprintTestCallback(scoped_ptr<Fingerprint> fingerprint) {
     // Verify that all fields Chrome can fill have been filled.
@@ -138,7 +138,7 @@ class AutofillRiskFingerprintTest : public InProcessBrowserTest {
   const gfx::Rect kScreenBounds;
   const gfx::Rect kAvailableScreenBounds;
   const gfx::Rect kUnavailableScreenBounds;
-  MessageLoop message_loop_;
+  base::MessageLoop message_loop_;
 };
 
 // This test is flaky on Windows. See http://crbug.com/178356.