

I guess the browser looks for a password field to insert your saved credentials. I notice this strange behavior on Chrome and Safari, when there are password fields in the same form.

The new fix works like before, but it handles the virtual keyboard: īecause the browser auto fills credentials to wrong text field!? Mobile Safari sets cursor in the field, but it does not show the virtual keyboard. Fix browser autofill in read-only and set writable on focus (click and tab) This workaround is in addition to apinstein's post about browser behavior. Sometimes even autocomplete=off would not prevent to fill in credentials into the wrong fields, but not a user or nickname field. I haven't yet investigated IE or Firefox thoroughly but will be happy to update the answer if others have info in the comments. However, adding this to the top of your form seems to disable the password autofill: This is quite a bad bug that hopefully, they will change the Safari behavior.

So just be sure to use 2 password fields (new and confirm new) for any forms where you allowĬhrome 34, unfortunately, will try to autofill fields with user/pass whenever it sees a password field.

Safari notices that there are 2 password fields and disables autocomplete in this case, assuming it must be a change password form, not a login form.If you can keep all password fields on a page by themselves, that's a great start as it seems that the presence of a password field is the main trigger for user/pass autocomplete to kick in.Unfortunately, bugs in the autocomplete implementations insert username and/or password info into inappropriate form fields, causing form validation errors, or worse yet, accidentally inserting usernames into fields that were intentionally left blank by the user. Long ago most password managers started ignoring autocomplete=off, and now the browsers are starting to do the same for username/password inputs only. Why? Many banks and other "high security" websites added autocomplete=off to their login pages "for security purposes" but this actually decreases security since it causes people to change the passwords on these high-security sites to be easy to remember (and thus crack) since autocomplete was broken. Most of the major browsers and password managers (correctly, IMHO) now ignore autocomplete=off.
