Logs different SaveCardPrompt histogram names depending on if user

components/autofill/core/browser/autofill_manager.cc

Index: components/autofill/core/browser/autofill_manager.cc
diff --git a/components/autofill/core/browser/autofill_manager.cc b/components/autofill/core/browser/autofill_manager.cc
index 6921626a500115c18287ed9fd16677a5b43629e3..b3a57d3aecc3f77e7a782d837650c9cf8a355725 100644
--- a/components/autofill/core/browser/autofill_manager.cc
+++ b/components/autofill/core/browser/autofill_manager.cc
@@ -284,6 +284,8 @@ void AutofillManager::RegisterProfilePrefs(
   registry->RegisterBooleanPref(prefs::kAutofillWalletImportEnabled, true);
   registry->RegisterBooleanPref(
       prefs::kAutofillWalletImportStorageCheckboxState, true);
+  registry->RegisterBooleanPref(prefs::kAutofillAcceptSaveCreditCardPromptState,

[Mathieu, 2017/04/26 14:31:17]

you are starting with a default state that the user has accepted previously.
Isn't that going to skew your metrics one way?

[csashi, 2017/04/26 17:58:31]

Done.

It seemed reasonable to assume that the bootstrap state is accept. I agree that
if we want to be more precise we should start with a default state of NULL and
have 3 metrics.

1. No suffix.
2. Previously accepted
3. Previously denied.

+                                true);
 }
 
 void AutofillManager::SetExternalDelegate(AutofillExternalDelegate* delegate) {