Remove base::MessageLoop::{Quit,QuitClosure} functions

win8/metro_driver/chrome_app_view.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "win8/metro_driver/stdafx.h"
 #include "win8/metro_driver/chrome_app_view.h"
 
 #include <corewindow.h>
 #include <windows.applicationModel.datatransfer.h>
 #include <windows.foundation.h>
@@ skipping 747 matching lines @@
   // Enter main core message loop. There are several ways to exit it
   // Nicely:
   // 1 - User action like ALT-F4.
   // 2 - Calling ICoreApplicationExit::Exit().
   // 3-  Posting WM_CLOSE to the core window.
   HRESULT hr = dispatcher->ProcessEvents(
       winui::Core::CoreProcessEventsOption
           ::CoreProcessEventsOption_ProcessUntilQuit);
 
   // Wind down the thread's chrome message loop.
-  base::MessageLoop::current()->Quit();
+  base::MessageLoop::current()->QuitWhenIdle();
 }
 
 void ChromeAppView::CheckForOSKActivation() {
   // Hack for checking if the OSK was displayed while we are in the foreground.
   // The input pane notifications which are supposed to fire when the OSK is
   // shown and hidden don't seem to be firing in Windows 8 metro for us.
   // The current hack is supposed to workaround that issue till we figure it
   // out. Logic is to find the OSK window and see if we are the foreground
   // process. If yes then fire the notification once for when the OSK is shown
   // and once for when it is hidden.
@@ skipping 428 matching lines @@
   CheckHR(core_app.As(&app_exit));
   globals.app_exit = app_exit.Detach();
 }
 
 IFACEMETHODIMP
 ChromeAppViewFactory::CreateView(winapp::Core::IFrameworkView** view) {
   globals.view = mswr::Make<ChromeAppView>().Detach();
   *view = globals.view;
   return (*view) ? S_OK :  E_OUTOFMEMORY;
 }