this is such an obvious use case, they basically threw a ton of web-apps/crms under the bus.

While I dislike this behavior of chrome, you should never be able to set a users password.

It is arrogant to assume this is true of every single use case.

I really can't think of a scenario where the end-user not being in full control of their credentials is good.

Are there situations in which it is easier if the admin can just reset it, sure. Is that a good idea, no.

Your mistake is thinking a login is a person and a person has an email.

I have run into all three of these scenarios:

1) A login for an administrator area on a server has a different login/password than the main area, and the browser always fills in the main login/password, even though I ask it not to. autocomplete=off would fix this.

2) A new user and edit user screens exist in web apps that are driven by users sign-ups. Sometimes these things need to be coordinated with other systems in a corporation and users do not always have their own email (I know this is a shock for you, but it is very common). autocomplete=off would fix this.

3) Using a remote admin tool to setup a datasource on a server, the username and password fields refer to database credentials, not a person. Yet Chrome keeps filling in my info. autocomplete=off would fix this.

i dunno why you're getting downvoted. you're right about this. but this doesn't apply to autofill behavior of non-password fields.