Add a new flag for HTTP-bad Phase 1 development work

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index 9ae01c4ec4c779bda2bc224a7fad1563ad25d488..73e80d08b2350980b0bf2591fa6e88767dce4c07 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -5255,13 +5255,16 @@ Keep your key file in a safe place. You will need it to create new versions of y
         Mark non-secure origins as non-secure
       </message>
       <message name="IDS_MARK_NON_SECURE_AS_DESCRIPTION" desc="Description of the 'Mark Non-Secure Origins As' lab.">
-        Mark non-secure origins as non-secure, or as "dubious".
+        Change the UI treatment for non-secure (HTTP) origins.

[elawrence, 2016/09/13 17:56:31]

Including periods in dropdown items is unusual on Windows.

That said, you are keeping the existing precedent for this flag, and this isn't
the only flag in chrome://flags to include a period (though most don't).

[felt, 2016/09/13 18:39:51]

Done.

       </message>
       <message name="IDS_MARK_NON_SECURE_AS_NEUTRAL">
-        Mark non-secure origins as neutral.
+        Always mark non-secure origins as neutral.
       </message>
       <message name="IDS_MARK_NON_SECURE_AS_NON_SECURE">
-        Mark non-secure origins as non-secure.
+        Always mark non-secure origins as non-secure.
+      </message>
+      <message name="IDS_MARK_NON_SECURE_AS_NON_SECURE_WITH_PASSWORDS">
+        Mark non-secure origins as non-secure when password or credit card fields are detected.
       </message>
       <message name="IDS_FLAGS_SAVE_PAGE_AS_MHTML_NAME" desc="Name of the 'Save Page as MHTML' lab.">
         Save Page as MHTML