Update behavior of one-click infobar to remove modal dialog, add "undo".

chrome/browser/ui/browser_window.h

Index: chrome/browser/ui/browser_window.h
diff --git a/chrome/browser/ui/browser_window.h b/chrome/browser/ui/browser_window.h
index 508249ae1f66626461f7897e58cfe4fbc0d72290..169582f2889b0ebb3b96256e7ffbc5cb4515e57f 100644
--- a/chrome/browser/ui/browser_window.h
+++ b/chrome/browser/ui/browser_window.h
@@ -50,6 +50,12 @@ enum DevToolsDockSide {
   DEVTOOLS_DOCK_SIDE_RIGHT = 1
 };
 
+// Callback type used with the ShowOneClickSigninBubble() method of class
+// BrowserWindow.  If the user chooses to accept the sign in, the callback
+// is called.  The boolean argument is true if the default sync settings should
+// be used, and false if the user wants to configure the settings.
+typedef base::Callback<void(bool)> OneClickSigninBubbleCallback;

[akalin, 2012/05/23 21:15:48]

I'm sorry to be a stickler about this, but:

- What happened to the enum? (instead of the bool) ( enum StartSyncMode {
SYNC_WITH_DEFAULT_SETTINGS, CONFIGURE_SYNC_FIRST }; )

- OneClickSigninBubbleCallback isn't very descriptive -- it doesn't tell me what
it actually does, which is to start sync.  Why not my suggested name,
StartSyncCallback?

- The natural place for the enum (and thus the callback) is to me
one_click_signin_sync_starter.h, which this file can include.  Having to pull in
browser_window.h (relatively large) just for StartSyncCallback seems suboptimal
to me.

[Roger Tawa OOO till Jul 10th, 2012/05/24 14:38:59]

Sorry Fred, my bad.  I was going to do the enum but forgot before sending the
review.  As for name of class I'm OK with that.

However, I don't think one_click_signin_sync_starter.h is the right place.  I do
think browser_window.h is the closest header file since the callback is needed
by any class that implements BrowserWindow or calls on BrowserWindow (which are
the various one click bubble implementations for the various platforms).  Its
not used at all by OneClickSigninSyncStarter.  Note that I could also declare
the type inside the class BrowserWindow so as to not pollute the namespace.

If you don't think browser_window.h is the right place, then I think the best
other alternative is to put it in its own header file, much like
base\callback_forward.h, and then include this header where needed.

+
 ////////////////////////////////////////////////////////////////////////////////
 // BrowserWindow interface
 //  An interface implemented by the "view" of the Browser window.
@@ -221,11 +227,10 @@ class BrowserWindow : public BaseWindow {
   virtual void ShowChromeToMobileBubble() = 0;
 
 #if defined(ENABLE_ONE_CLICK_SIGNIN)
-  // Shows the one-click sign in bubble.  The given closures are run
-  // when their corresponding links are clicked.
+  // Shows the one-click sign in bubble.  If the user chooses to accept the
+  // sign in, |start_sync_callback| is called.
   virtual void ShowOneClickSigninBubble(
-      const base::Closure& learn_more_callback,
-      const base::Closure& advanced_callback) = 0;
+      const OneClickSigninBubbleCallback& start_sync_callback) = 0;
 #endif
 
   // Whether or not the shelf view is visible.