Use a password manager app: This is the easiest and, believe it or not, most secure way to manage all your online logins.The list can get a tad unwieldy once you hit more than 50 logins to keep track of. Write all your different passwords down: This “pen and paper” method works, but only if you’re sitting at your desk.If somebody gets a hold of this one password, they can hack your entire online life Use the same password for all your logins: This is one of many bad online habits you need to break.While this is more than most, chances are that you also have more online usernames and passwords than you realize. This includes everything from banking to frequent flyer programs to my home insurance provider. You can just set the password input to readonly the change its state ĭocument.getElementById('password').Be sure to subscribe to the All Things Secured YouTube channel!Ĭurrently, I have 298 327 378 different online logins that I have to manage. You can fix this by adding hidden fields at the top of your form to distract the browser but there seems to be a workaround to fix this issue caused accidentally by the browser.

This seems to be an issue/advantage that browsers force pages to behave this way, and absolutely this is not fixed when setting autocomplete='new-password' or even if you set the value to off. This is not exactly a dup from 'how to use autocomplete=new-password' as the behavior seems to have changed or is ill-documented. The first page triggers the 'save login' feature, but the second should NOT use that info to autocomplete the password - yet, it does. They can be served from any HTTP server (e.g. I created two very simple examples to remove any external interference to the issue. It's supposed to be supported in both browsers. I'm trying to add autocomplete=new-password to some user-editing forms, but it fails to follow the correct behavior in Chrome 79 and Firefox 71.

One password extension firefox