UMA histogram of user action on multi-account password update bubble.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 82f27f48442fb8c9137b8a7aa56e46e6be041ac0..516788b588c7915c8869229535cac3509f10bd73 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -32533,6 +32533,15 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <summary>An error on LoginDatabase initialization.</summary>
 </histogram>
 
+<histogram name="PasswordManager.MultiAccountPasswordUpdateAction"
+    enum="MultiAccountUpdateBubbleUserAction">
+  <owner>dvadym@chromium.org</owner>
+  <summary>
+    A user action when the password update bubble with multiple accounts is

[Ilya Sherman, 2016/01/14 01:07:24]

nit: s/the/a

[dvadym, 2016/01/14 10:44:32]

Done.

+    shown.
+  </summary>
+</histogram>
+
 <histogram name="PasswordManager.NumPasswordsDeletedByBulkDelete">
   <owner>vabr@chromium.org</owner>
   <summary>
@@ -70929,6 +70938,19 @@ To add a new entry, add it with any value and run test to compute valid value.
   <int value="11" label="AC3"/>
 </enum>
 
+<enum name="MultiAccountUpdateBubbleUserAction" type="int">
+  <int value="0" label="DEFAULT_ACCOUNT_MATCHED_BY_PASSWORD_USER_CHANGED"/>
+  <int value="1" label="DEFAULT_ACCOUNT_MATCHED_BY_PASSWORD_USER_NOT_CHANGED"/>
+  <int value="2"
+      label="DEFAULT_ACCOUNT_MATCHED_BY_PASSWORD_USER_REJECTED_UPDATE"/>
+  <int value="3" label="DEFAULT_ACCOUNT_PREFERRED_USER_CHANGED"/>
+  <int value="4" label="DEFAULT_ACCOUNT_PREFERRED_USER_NOT_CHANGED"/>
+  <int value="5" label="DEFAULT_ACCOUNT_PREFERRED_USER_REJECTED_UPDATE"/>
+  <int value="6" label="DEFAULT_ACCOUNT_FIRST_USER_CHANGED"/>
+  <int value="7" label="DEFAULT_ACCOUNT_FIRST_USER_NOT_CHANGED"/>
+  <int value="8" label="DEFAULT_ACCOUNT_FIRST_USER_REJECTED_UPDATE"/>

[Ilya Sherman, 2016/01/14 01:07:24]

Optional nit: I'd recommend more human-friendly labels, though these are ok if
you think it's important to maintain consistency with the C++ enum names.

[dvadym, 2016/01/14 10:44:32]

Thanks, I'd rather leave C++ enum names in order to easy match with code.

+</enum>
+
 <enum name="MultiProfileSessionMode" type="int">
   <int value="0" label="Single user mode"/>
   <int value="1" label="Side by side mode"/>