• estark's avatar
    Don't limit 'Login not secure' warning to password fields · c97dee45
    estark authored
    Per the specs at go/fns-ui-spec, the "Login not secure" warning should
    show up in username fields as well as password fields. Which makes sense
    because usernames are sensitive information too. Thus, this CL populates
    the "Login not secure" warning in the suggestions dropdown of a password
    form regardless of whether the field is a password field or not.
    
    BUG=675696
    TEST=Enable #enable-http-form-warning in chrome://flags and relaunch
    Chrome. Save a username/password in the Name/Password form in
    http://rsolomakhin.github.io/autofill/. Focus the "Name" field and
    observe a "Login not secure" warning in the autofill dropdown.
    
    Review-Url: https://codereview.chromium.org/2585173006
    Cr-Commit-Position: refs/heads/master@{#439837}
    c97dee45
autofill_strings.grdp 20.8 KB