3 ms·
>I'm glad this is happening, although I'm more excited for the day when they start very obviously marking password input fields as "NOT SECURE" when they are us
by Santosh83 9y ago
>I'm glad this is happening, although I'm more excited for the day when they start very obviously marking password input fields as "NOT SECURE" when they are used on HTTP sites.
Mozilla already does this with Firefox:
https://support.mozilla.org/en-US/kb/insecure-password-warning-firefox?as=u&utm_source=inproduct https://support.mozilla.org/en-US/kb/insecure-password-warni...
- schoen 9y agoMaybe Klathmon was envisioning it appearing inside the password field itself (not just in the browser chrome)?
- Ajedi32 9y agoFirefox _does_ do it in the password field itself: https://prod-cdn.sumo.mozilla.net/uploads/gallery/images/2017-04-21-23-52-53-ba340d.png https://prod-cdn.sumo.mozilla.net/uploads/gallery/images/201... Doesn't seem like Chrome's planning to do it that way though.
- schoen 9y agoOh yeah, thanks for pointing that out! Maybe Chrome would be up for it at some point in the future as HTTP form submissions become rarer, though I don't know how they made this decision. Edit: Amusingly, even though I normally use Firefox, I haven't noticed this UI element recently because I'm so conscious of HTTPS—working on Let's Encrypt and support for it—that I rarely even try to enter information into a non-HTTPS site in the first place. :-) (so I might not be quite the target audience for this notification)