Almost all of its uses are dead code paths since we shunted it to neutral a year ago [1].
Manifestations:
- content::SECURITY_STYLE_WARNING
- SecurityStateModel::SECURITY_WARNING
- Generated for Android: ConnectionSecurityLevel.SECURITY_WARNING
- Security[Agent].SecurityState.warning (DevTools)
- Generated for the browser process: content::devtools::security::kSecurityStateWarning
After looking at all uses of these constants, I saw only one potential non-dead code path [2]:
case SecurityStateModel::SECURITY_POLICY_WARNING:
return content::SECURITY_STYLE_WARNING;
I believe the right thing to do in that case is to map SECURITY_POLICY_WARNING it to SECURITY_STYLE_UNAUTHENTICATED instead.
I'm going to try uploading a CL with all the removed values and see if it still passes all tests.
[1] https://security.googleblog.com/2015/10/simplifying-page-security-icon-in-chrome.html
[2] https://chromium.googlesource.com/chromium/src/+blame/master/chrome/browser/ssl/chrome_security_state_model_client.cc#77
Comment 1 by lgar...@chromium.org
, Sep 10 2016