Google Search. The search form has autocomplete=off so that it can be replaced with Google Suggest.

It's still useful to control unwanted autocomplete behavior. With Chrome, for example, if you have a form with fields name "name" and "state", even if they have zero to do with a personal name or state of residency, users still get their normal autocomplete in "name". When you select a name, if that autocomplete entry has address information attached, Chrome helpfully fills in "state" with "CA". Even if "CA" makes zero sense for that field.

Almost all other times, though, I'm with you: slap them!

Sometimes when dealing with high security you have to input a nonce. Autocomplete would be a nuisance.

Credit card number fields?

My browser can type my credit card information faster than I can.

Honestly, `autocomplete=off` is an unwelcome attempt to try to save me from myself.

I always thought of `autocomplete=off` to guard shared computers. I've turned it off for CC fields but the intention is that if you're on a shared computer the security outweighs the browser remembering something such as a credit card number.

I don't believe people type values into a form realizing at the moment that the browser is saving it for future uses.

They intend for that to be stored. http://www.chromium.org/developers/using-requestautocomplete

The change that they're making to Chrome only affects password fields.

+1 and even more importantly CVV fields.