Enhance FormNotSecure UX when on broken HTTPS |
|||||||||
Issue descriptionWhen a broken-https page loads a password form and there is login data stored, the autofill dropdown should have a second row below the "Login not secure" warning that says "Login autofilling disabled".
,
Dec 10 2016
,
Dec 13 2016
,
Dec 15 2016
,
Jan 26 2017
When on broken HTTPS (after clickthrough a certificate error): 1. If the user has credentials stored for the site, show both "[Login not secure] and [Login autofilling disabled]" rows in the autofill dropdown. 2. If the user does not have credentials stored for the site, show a "[Login not secure]" row in the autofill dropdown. These two autofill messages are added in different places. The "No accounts stored" codepath only looks to see if IsOriginSecure(url) without examining the security state of the context.
,
May 2 2017
,
Sep 29 2017
,
Nov 10 2017
,
Nov 11 2017
Feature isn't launching |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rouslan@chromium.org
, Dec 9 2016