7 ms·
This totally works in latest Chrome/FF/Safari https://codesandbox.io/s/static-jkvzs https://codesandbox.io/s/static-jkvzs https://jkvzs.codesandbox.io/ https:
by analogmemory 7y ago
This totally works in latest Chrome/FF/Safari
https://codesandbox.io/s/static-jkvzs https://codesandbox.io/s/static-jkvzs
https://jkvzs.codesandbox.io/ https://jkvzs.codesandbox.io/
The other trick is to add a random string/number in from of the name attribute e.g. name="348349_name". This prevents autofill. Interestingly 1Password and LastPass are smart enough to infer that it's a name or email field.
For the honeypot, random number + word makes it ignored by autofill/1password
- fybe 7y agoMy 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