3 ms·

This is about more than just password fields, although that is a big one. I can give you a legitimate, actual use case where I had to develop a workaround: a p

This is about more than just password fields, although that is a big one. I can give you a legitimate, actual use case where I had to develop a workaround: a page where an admin can change the password for a user. Under no circumstances would an autofill be desirable on that page, yet Chrome thinks it knows best.

LeifCarrotson 5y ago
Edit: I stand corrected, this approach worked for me when I was building an internal app but apparently doesn't work at other times. Just don't give the input an "id=password" and Chrome won't throw your password into it. It's just a label, the autofill is because it matches all the other sites where you do want Chrome to autofill your password.
- jaywalk 5y ago
  Ha, how did you come up with that nonsense solution? You've obviously never actually dealt with this if you think that would work.
  - dariusj18 5y ago
    Yeah, Chrome can be very devious at figuring it out. I've had success using `autocomplete="new-password"` at least.
codyswann 5y ago
set autoFill to "new-password"