[Autofill] Credit Card Assist Infobar

chrome/browser/ui/autofill/chrome_autofill_client.cc

Index: chrome/browser/ui/autofill/chrome_autofill_client.cc
diff --git a/chrome/browser/ui/autofill/chrome_autofill_client.cc b/chrome/browser/ui/autofill/chrome_autofill_client.cc
index e9d87562a8b12e079bc893994071e8c0457f3528..e0f16a5dfde51308a15a67eb57fde91478fc3f3d 100644
--- a/chrome/browser/ui/autofill/chrome_autofill_client.cc
+++ b/chrome/browser/ui/autofill/chrome_autofill_client.cc
@@ -14,7 +14,6 @@
 #include "chrome/browser/autofill/personal_data_manager_factory.h"
 #include "chrome/browser/autofill/risk_util.h"
 #include "chrome/browser/browser_process.h"
-#include "chrome/browser/infobars/infobar_service.h"
 #include "chrome/browser/password_manager/chrome_password_manager_client.h"
 #include "chrome/browser/profiles/profile.h"
 #include "chrome/browser/profiles/profile_manager.h"
@@ -62,6 +61,9 @@
 #if defined(OS_ANDROID)
 #include "base/android/context_utils.h"
 #include "chrome/browser/android/signin/signin_promo_util_android.h"
+#include "chrome/browser/infobars/infobar_service.h"
+#include "chrome/browser/ui/android/infobars/autofill_credit_card_filling_infobar.h"
+#include "components/autofill/core/browser/autofill_credit_card_filling_infobar_delegate_mobile.h"
 #include "components/autofill/core/browser/autofill_save_card_infobar_delegate_mobile.h"
 #include "components/autofill/core/browser/autofill_save_card_infobar_mobile.h"
 #include "components/infobars/core/infobar.h"
@@ -211,6 +213,27 @@ void ChromeAutofillClient::ConfirmSaveCreditCardToCloud(
 #endif
 }
 
+void ChromeAutofillClient::ConfirmCreditCardFillAssist(
+    const CreditCard& card,
+    const base::Closure& callback) {
+#if defined(OS_ANDROID)

[Peter Kasting, 2016/08/03 02:25:40]

If it's really true that desktop is "never going to want an infobar", as Evan
said, why is AutofillCreditCardFillingInfoBarDelegateMobile even defined in
components/ to begin with?  Why isn't it defined on the embedder side, in
Android-specific files?  This would allow you to implement the Create() function
in the way I asked without having to make a complicated, multi-hop system of
calls back and forth across the component interface, and without having to add
things like set_was_shown().

[Mathieu, 2016/08/03 18:34:44]

I would like to keep the delegate inside components/ because it will be reused
for iOS, similar to how the "save card" infobar delegate is reused across mobile
platforms (with the platform-specific infobar instantiation code in their
appropriate directories). I think this way is good.

+  std::unique_ptr<infobars::InfoBar> infobar(
+      base::WrapUnique(new AutofillCreditCardFillingInfoBar(

[Peter Kasting, 2016/08/03 02:25:40]

Nit: Use MakeUnique in newly-written code (WrapUnique is mostly for
auto-conversions).

[Mathieu, 2016/08/03 18:34:44]

Done.

+          base::WrapUnique(new AutofillCreditCardFillingInfoBarDelegateMobile(
+              card, callback)))));
+  if (infobar) {
+    infobars::InfoBar* added_infobar =
+        InfoBarService::FromWebContents(web_contents())
+            ->AddInfoBar(std::move(infobar));
+    if (added_infobar) {
+      static_cast<AutofillCreditCardFillingInfoBarDelegateMobile*>(

[Peter Kasting, 2016/08/03 02:25:40]

Nit: Just save this raw pointer off when you first create the delegate, before
passing to the infobar:

  auto infobar_delegate = ...;
  auto* raw_delegate = infobar_delegate.get();
  ...;
  raw_delegate->set_was_shown(true);

[Mathieu, 2016/08/03 18:34:44]

Done.

+          added_infobar->delegate())
+          ->set_was_shown(true);
+    }
+  }
+#endif
+}
+
 void ChromeAutofillClient::LoadRiskData(
     const base::Callback<void(const std::string&)>& callback) {
   ::autofill::LoadRiskData(0, web_contents(), callback);