Add Views implementation of ProfileSigninConfirmationDialog.

chrome/browser/ui/sync/one_click_signin_sync_starter.cc

Index: chrome/browser/ui/sync/one_click_signin_sync_starter.cc
diff --git a/chrome/browser/ui/sync/one_click_signin_sync_starter.cc b/chrome/browser/ui/sync/one_click_signin_sync_starter.cc
index dc1b99838f723cee569fc91ca919e0446c5ea41f..068df48407f806234387372d074259f845144a0d 100644
--- a/chrome/browser/ui/sync/one_click_signin_sync_starter.cc
+++ b/chrome/browser/ui/sync/one_click_signin_sync_starter.cc
@@ -23,10 +23,12 @@
 #include "chrome/browser/sync/profile_sync_service_factory.h"
 #include "chrome/browser/sync/sync_prefs.h"
 #include "chrome/browser/ui/browser.h"
+#include "chrome/browser/ui/browser_dialogs.h"
 #include "chrome/browser/ui/browser_finder.h"
 #include "chrome/browser/ui/browser_navigator.h"
 #include "chrome/browser/ui/browser_window.h"
 #include "chrome/browser/ui/chrome_pages.h"
+#include "chrome/browser/ui/tabs/tab_strip_model.h"
 #include "chrome/browser/ui/webui/signin/login_ui_service.h"
 #include "chrome/browser/ui/webui/signin/login_ui_service_factory.h"
 #include "chrome/browser/ui/webui/signin/profile_signin_confirmation_dialog.h"
@@ -140,7 +142,23 @@ void OneClickSigninSyncStarter::OnRegisteredForPolicy(
   policy_client_.swap(client);
 
   // Allow user to create a new profile before continuing with sign-in.
-  ProfileSigninConfirmationDialog::ShowDialog(
+  Browser* browser =
+      chrome::FindBrowserWithProfile(profile_, chrome::GetActiveDesktop());
+  if (!browser) {
+    DLOG(WARNING) << "No browser found to display the confirmation dialog";

[Peter Kasting, 2013/05/15 00:11:03]

In most Chrome code we try to avoid logging because we usually don't have a good
way of getting the log data and doing something useful with it anyway.  Do you
really need these logs?

It would be clearer to either just handle these cases and return (if they can
actually ever happen) or DCHECK and don't handle them if they can't actually
occur.

[Andrew T Wilson (Slow), 2013/05/16 08:00:30]

Do we really have any restrictions on adding DLOGs()? This is often useful when
debugging failed tests, especially for exceptional conditions.

[Peter Kasting, 2013/05/16 21:57:39]

In the particular code here, it seems like either these conditions are
impossible -- in which case we should at most DCHECK() them, and not handle
them, which will be just as informative in a test failure -- or they're
reasonable for some particular scenario(s), in which case we really shouldn't be
logging them, we should just silently handle them.

Logging here would be more appropriate if you're in the process of trying to
make these conditions hold, but you think they currently don't, and you think
there are important cases that will break if using a DCHECK, but you have a
specific plan on how to locate the log output and use it to finish off the
fixes.

In general, there aren't hard-and-fast rules so much as a desire to have no
middle ground between "this can happen" and "this cannot happen".  Something
like DLOG(WARNING) is worrisome in the same sort of way that handling DCHECK
failures is worrisome -- it becomes unclear precisely what the intent of the
code or the magnitude of any problem is, and over time we tend toward console
spew about issues no one is sure are important or aware of how to deal with. 
For short-term changes, logs are welcome if they're useful, it's just not good
to have them persist for a significant length of time.

[dconnelly, 2013/05/17 13:01:55]

Done: removed the logging and kept the handling.  This situation can occur if
the user starts signin and then closes the browser before this is reached.

+    CancelSigninAndDelete();
+    return;
+  }
+  content::WebContents* web_contents =
+      browser->tab_strip_model()->GetActiveWebContents();
+  if (!web_contents) {
+    DLOG(WARNING) << "No web contents found to display the confirmation dialog";
+    CancelSigninAndDelete();
+    return;
+  }
+  chrome::ShowProfileSigninConfirmationDialog(
+      browser,
+      web_contents,
       profile_,
       signin->GetUsernameForAuthInProgress(),
       base::Bind(&OneClickSigninSyncStarter::CancelSigninAndDelete,