UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. We have a page that stores a private key for authentication.
2. That private key is stored in an html password field.
3. There are other input fields on the page, none of which are intended to be for the username.

What is the expected behavior?
The password field is pre-populated from the database with a stored key. Other fields are not auto populated with usernames/passwords.

What went wrong?
A field is chosen and assumed to be the username field, and auto populated with username. The password field is auto-populated with the recent password.

Did this work before? Yes 

Chrome version: 51.0.2704.84  Channel: n/a
OS Version: 6.3
Flash Version: Shockwave Flash 23.0 r0

This is simply obnoxious behavior. Since Chrome has made the decision to ignore auto-complete = false, removing the ability for developers to control their pages behaviors, we are forced into extreme workarounds. I have generally had the impression that Chrome was a good browser with great tools. My entire team has been cursing Chrome and the obnoxious behavior. This needs to change. It is simply obnoxious.