My mistake, looked into it again and it seems Chrome enabled it again in Chrome 68: https://stackoverflow.com/questions/25823448/ng-form-and-autocomplete-off/3

My mistake, looked into it again and it seems Chrome enabled it again in Chrome 68: https://stackoverflow.com/questions/25823448/ng-form-and-autocomplete-off/39689037#39689037 https://stackoverflow.com/questions/25823448/ng-form-and-aut... Firefox had it disabled too but enabled it back again: https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion#The_autocomplete_attribute_and_login_fields https://developer.mozilla.org/en-US/docs/Web/Security/Securi... And IE is just a cluster f. My point being, Autocomplete off is not a valid solution as it can break at an updates notice, and the code hacks, while may work, are a pain to deal with