Add a new flag for HTTP-bad Phase 1 development work
This extends the #mark-non-secure-as flag to use for the HTTP-bad phase
1 (passwords and CC form detection) work. It currently behaves exactly
like the existing kMarkNonSecureAsNeutral switch, although presumably
that will change as we make progress.
BUG=646221
Review-Url: https://codereview.chromium.org/2337103002
Cr-Commit-Position: refs/heads/master@{#418860}
diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index 82035aa0..b57dced 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -200,7 +200,10 @@
security_state::switches::kMarkNonSecureAsNeutral},
{IDS_MARK_NON_SECURE_AS_NON_SECURE,
security_state::switches::kMarkNonSecureAs,
- security_state::switches::kMarkNonSecureAsNonSecure}};
+ security_state::switches::kMarkNonSecureAsNonSecure},
+ {IDS_MARK_NON_SECURE_WITH_PASSWORDS_OR_CC_AS_NON_SECURE,
+ security_state::switches::kMarkNonSecureAs,
+ security_state::switches::kMarkNonSecureWithPasswordsOrCcAsNonSecure}};
const FeatureEntry::Choice kDataReductionProxyLoFiChoices[] = {
{ IDS_GENERIC_EXPERIMENT_CHOICE_DEFAULT, "", "" },
