Chrome is fun, today I learned you cannot turn off auto-complete for a page in chrome. Possibly some really creative hacks can do it but those seem to be "fixed" every so often as well. Which is great when you're building a HIPAA compliant page and would prefer that people's medical information not get cached by chrome (and then uploaded to their cloud storage if you're logged in).
> Chrome is fun, today I learned you cannot turn off auto-complete for a page in chrome.
Because people were abusing it left-and-right to prevent password managers, and as e.g. banks (my own bank did this...) rarely listen to customers, Google instead decided to disable that opt-out for everyone instead.
I remember reading that the Chrome team made a point of forcing autocomplete for password fields (out of some opinions about built-in password managers). But I didn't know they were expanding that sentiment to all kinds of autocompletion.
Not that this would surprise me with Chrome's general attitude...
I agree with Chrome's decision here. The data remains the property of the user, they are free to cache it on their machine or upload it to Google if they so desire. Pages that disable autocomplete (or break it with hacks) should die.
Where did I say URL? I'm talking a POST based form.
Put a value into it a text field and Chrome will helpfully save it for future auto-completion. Then it'll upload it to your account on their cloud if you're logged into an account. How do you think it's able to fill out your name, address, etc. on all those web forms?
I'm sorry. I'm out of date it seems. I thought autocomplete="false" worked for non authentication/non common fields. I'll have to check this out in the office later.
