3 ms·
What you raise is a valid concern, but letting websites decide on enabling/disabling auto-complete is solving it entirely wrong way around. If local admin is i
by gmazza 10y ago
What you raise is a valid concern, but letting websites decide on enabling/disabling auto-complete is solving it entirely wrong way around.
If local admin is incapable of configuring user accounts, how are websites supposed to figure out who is who, and which browser is on shared computer?
After all, if managing user accounts is too hard for said admin (or we are talking about a shared PC in a library, which doesn't have user accounts as a matter of principle) - just make browser always start in private/incognito mode on shared computer. It is as easy as adding command-line argument "--private-window" for firefox or "--temp-profile" for chrome. That's it. Window closed - autocomplete gone. Problem solved.
- arenaninja 10y agoAssumes a competent, dedicated local admin is on staff. This is not the case at about 75% of the SMBs I've come into contact with over the past two years
- acdha 10y agoModern operating systems have a guest mode which doesn't preserve state across sessions - if they cannot manage something this easy, everyone should be using a guest login.
- kalleboo 10y agoWebsites will always have the ability to disable auto-complete though. Just now it will be though a series of ever-increasingly insane hacks found on StackOverflow (culminating in a custom JavaScript textfield with broken accessibility/internationalization)