Enable Update Password UI on iOS behind a flag

ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm

Index: ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm
diff --git a/ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm b/ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm
index f24d098b23fa96cebb9cc813118274b4803b46b4..b538080f8568251457c109db4e9a4a6b35e51bda 100644
--- a/ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm
+++ b/ios/chrome/browser/passwords/ios_chrome_password_manager_client.mm
@@ -15,9 +15,11 @@
 #include "components/password_manager/core/common/password_manager_pref_names.h"
 #include "components/signin/core/browser/signin_manager_base.h"
 #include "ios/chrome/browser/browser_state/chrome_browser_state.h"
+#include "ios/chrome/browser/experimental_flags.h"
 #include "ios/chrome/browser/passwords/ios_chrome_password_store_factory.h"
 #include "ios/chrome/browser/signin/signin_manager_factory.h"
 #include "ios/chrome/browser/sync/ios_chrome_profile_sync_service_factory.h"
+

[vabr (Chromium), 2016/07/05 14:30:57]

nit: Why this blank line? Normally the non-system #includes are in one block
except for #ifdef parts.

[Jackie Quinn, 2016/07/05 15:12:36]

user error. Fixed.

 #include "url/gurl.h"
 
 using password_manager::PasswordFormManager;
@@ -74,7 +76,13 @@ bool IOSChromePasswordManagerClient::PromptUserToSaveOrUpdatePassword(
     bool update_password) {
   if (form_to_save->IsBlacklisted())
     return false;
-  [delegate_ showSavePasswordInfoBar:std::move(form_to_save)];
+
+  if (experimental_flags::IsUpdatePasswordUIEnabled() && update_password) {
+    [delegate_ showUpdatePasswordInfoBar:std::move(form_to_save)];
+  } else {
+    [delegate_ showSavePasswordInfoBar:std::move(form_to_save)];

[vabr (Chromium), 2016/07/05 14:30:57]

This seems like it would start showing the "save password" infobar for password
updates if the flag is off. It should be rather:
if (update_password) {
  if (/*flag set*/)
    /*show update infobar*/
} else {
  /*show save infobar*/
}

[Jackie Quinn, 2016/07/05 15:12:36]

I had it this way since it was always showing the save infobar anyways. Happy to
change it though :-)

[vabr (Chromium), 2016/07/05 15:32:17]

Oh, you are right, Jackie, your patch set 4 keeps the original behaviour. In
that case I would suggest to keep it (= what you had in patch set 4). Sorry for
the back and forth.

Just out of curiosity, does iOS (without the change password support enabled)
prompt to save if you update a password? Looking at Android, in its section of
ChromePasswordManagerClient::PromptUserToSaveOrUpdatePassword, it does exactly
what you do here in patch set 4. Still, it updates silently. I have no idea why,
need to have a look later.

+  }
+
   return true;
 }