Update devtools security panel for HTTP-bad

components/security_state/security_state_model.h

Index: components/security_state/security_state_model.h
diff --git a/components/security_state/security_state_model.h b/components/security_state/security_state_model.h
index 9bcfbc6ccd554e0b5a53a979848dd361e2d85331..235c6b5e224211fe15b3e8b59c893d6fda2f05e4 100644
--- a/components/security_state/security_state_model.h
+++ b/components/security_state/security_state_model.h
@@ -136,6 +136,10 @@ class SecurityStateModel {
 
     // True if pinning was bypassed due to a local trust anchor.
     bool pkp_bypassed;
+
+    // True if the page displayed sensitive user data inputs (like a
+    // password or credit card) on an HTTP page.
+    bool displayed_private_user_data_input_on_http;

[lgarron, 2016/10/19 20:46:23]

Would it be worth keeping track of the two cases (passwords/credits) using a
mask?

[estark, 2016/10/19 21:02:18]

I thought about it, but thought that we could always do that later if we need it
-- no need for it now.

   };
 
   // Contains the security state relevant to computing the SecurityInfo