Upstream changes needed by Android auto-login.

chrome/browser/infobars/infobar_delegate.h

Index: chrome/browser/infobars/infobar_delegate.h
diff --git a/chrome/browser/infobars/infobar_delegate.h b/chrome/browser/infobars/infobar_delegate.h
index e3ddb70508eee055e8d678d982c992140c89c3e7..b2474d32218a378f87af0fabaff343ceb7192484 100644
--- a/chrome/browser/infobars/infobar_delegate.h
+++ b/chrome/browser/infobars/infobar_delegate.h
@@ -10,6 +10,7 @@
 #include "base/string16.h"
 #include "webkit/glue/window_open_disposition.h"
 
+class AutoLoginInfoBarDelegate;
 class ConfirmInfoBarDelegate;
 class ExtensionInfoBarDelegate;
 class InfoBar;
@@ -97,6 +98,7 @@ class InfoBarDelegate {
   virtual Type GetInfoBarType() const;
 
   // Type-checking downcast routines:
+  virtual AutoLoginInfoBarDelegate* AsAutoLoginInfoBarDelegate();

[Peter Kasting, 2012/06/27 17:39:05]

Why are you adding this?  You don't call it directly and we try very hard not to
add new ones of these.  Normally code that needs to cast can just static_cast<>
because it knows it has an auto-login infobar.

[Philippe, 2012/06/28 09:24:00]

I understand your concern here. This CL only upstreams the changes we made on
the chromium side. We also have the app side which directly uses this class (and
this method).

Unfortunately our current implementation on the app side does something like
that:

if (delegate->AsAutoLoginInfoBarDelegate())
  AddAutoLoginInfoBar(delegate);
else if (delegate->AsConfirmInfoBarDelegate())
  AddConfirmInfoBar(delegate);

I don't think we can easily get rid of this method without introducing a visitor
which wouldn't be better in this particular case (this would probably involve
much more boilerplate code).

   virtual ConfirmInfoBarDelegate* AsConfirmInfoBarDelegate();
   virtual ExtensionInfoBarDelegate* AsExtensionInfoBarDelegate();
   virtual InsecureContentInfoBarDelegate* AsInsecureContentInfoBarDelegate();