21–30 of 74 posts
Web devs can recommend input fields not use autocomplete: http://www.w3schools.com/tags/att_input_autocomplete.asp It's considered good practice to use it on login fields, but otherwise depends on whether you think security or user preference should take priority.
Safari tells you what is actually going to autocomplete, so you could easily catch stuff that should not be sent...
Doesn't seem to be an issue in Firefox, as far as I can tell. Certainly didn't fill any other fields for me.
Fixed that for you.
This is weird, I'm on chrome but it doesn't happen for me...
well I don't get the justification for the headline
Web devs can recommend input fields not use autocomplete: http://www.w3schools.com/tags/att_input_autocomplete.asp It's considered good practice to use it on login fields, but otherwise depends on whether you think security or user preference should take priority.
Turning off autocomplete on login fields doesn't make that form more secure, and it does annoy users.
As kalleboo says, it probably reduces security as your users change to easy to type passwords, or keep needing password resets.
Safari tells you what is actually going to autocomplete, so you could easily catch stuff that should not be sent...
This is true, and actually a pretty smart feature, but you have to take the time to double-check (which I suspect most users won't).
[1] https://www.evernote.com/shard/s356/sh/dcf7867e-eb16-4e0e-83...
One might even classify this as a bug.