“autocomplete=off is ignored on non-login input elements”

Re:“autocomplete=off is ignored on non-login input elements” by timv on Wednesday June 15, 2016 @09:36PM (#11913406)

This!

I have previously wasted so much time working around this browser behaviour.

The trick I use now is to add in a hidden (via CSS) pair on inputs earlier on the page, that do nothing. The browser fills those in, and leaves the real password admin fields empty.

[ Parent | on HN ]

Re:“autocomplete=off is ignored on non-login input elements” by zimpenfish on Thursday June 16, 2016 @12:39AM (#11914024)

I might be missing something subtle or obvious but can't you just give the inputs different names? Is it such a trauma to handle that case in the backend? e.g.

<input name='admin-user'><input name='admin-pass'>?

(Now if Chrome is auto{fill,complet}ing those with usernames + passwords, that's definitely a disastrous bug.)

[ Parent | on HN ]

Re:“autocomplete=off is ignored on non-login input elements” by timv on Thursday June 16, 2016 @09:11AM (#11915820)

Now if Chrome is auto{fill,complet}ing those with usernames + passwords, that's definitely a disastrous bug

You say "bug", they say "works as designed".

[ Parent | on HN ]

Re:“autocomplete=off is ignored on non-login input elements” by tacone on Thursday June 16, 2016 @04:11PM (#11918535)

Interesting trick.

[ Parent | on HN ]