4 ms·

I've yet to find a time when autocomplete has been disabled that I've not wanted to slap the web designer. Most every one has been on some sort of common addres

I've yet to find a time when autocomplete has been disabled that I've not wanted to slap the web designer. Most every one has been on some sort of common address form. My browser knows my address. I don't want to type it. You'll get better results from my browser than from me typing, always.

deleted 13y ago
[deleted]
voltagex_ 13y ago
Credit card number fields?
- ChristianBundy 13y ago
  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.
  - jmathai 13y ago
    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.
- jfoster 13y ago
  The change that they're making to Chrome only affects password fields.
- bdg 13y ago
  They intend for that to be stored. http://www.chromium.org/developers/using-requestautocomplete http://www.chromium.org/developers/using-requestautocomplete
- yogo 13y ago
  +1 and even more importantly CVV fields.
erichurkman 13y ago
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!
nostrademons 13y ago
Google Search. The search form has autocomplete=off so that it can be replaced with Google Suggest.
pgsandstrom 13y ago
Sometimes when dealing with high security you have to input a nonce. Autocomplete would be a nuisance.

deleted 13y ago

[deleted]

voltagex_ 13y ago

Credit card number fields?

ChristianBundy 13y ago
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.
- jmathai 13y ago
  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.
jfoster 13y ago
The change that they're making to Chrome only affects password fields.
bdg 13y ago
They intend for that to be stored. http://www.chromium.org/developers/using-requestautocomplete http://www.chromium.org/developers/using-requestautocomplete
yogo 13y ago
+1 and even more importantly CVV fields.

erichurkman 13y ago

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!

nostrademons 13y ago

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

pgsandstrom 13y ago

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