11 ms·
The problem is that some sites decided to use autocomplete=off to impose their feeling about password managers on users and make them more difficult to use. It'
by Spivak 9y ago
The problem is that some sites decided to use autocomplete=off to impose their feeling about password managers on users and make them more difficult to use. It's the same reason I have to turn off clipboard events because some sites think it's okay to block copy/paste.
- hbbio 9y agoPassword managers use browsers plugins, and as such can modify pages before they render as much as they like.
- pluma 9y agoHow is this different from websites that think it's okay to force you to abide by ridiculous password restrictions (e.g. 6-8 characters, must include digits, upper- and lowercase letters, and special characters but no quotation marks or any known SQL keywords)? The right thing to do is to bring the issue up with whoever is running the website. If they decide not to act on it because they think they know security/UX better than Google/you, they're stuck with crappier security/UX and the market should sort it out. I've actually managed to convince a company to stop prohibiting copy-paste on logins by pointing them at the new NIST password guidelines. I don't expect this to work for every company, but if they intentionally don't change, it's okay to name and shame them for it. Whether it's a UX sin or security voodoo.
- deleted 9y ago[deleted]
- biotech 9y ago> How is this different from websites that think it's okay to force you to abide by ridiculous password restrictions The difference is that disabling of "autocomplete" is a user interface issue, and can be addressed by the browser I use. The problem of ridiculous password restrictions is not usually something that can be controlled by the client. I like the idea of convincing IT to change crazy password policies, but I don't have the mental energy to navigate these huge bureaucracies.
- mcv 9y agoI'm all for allowing the user to control whether autocomplete is or isn't respected. But the browser breaking web standards to force certain choices on the user is about the worst possible way to go about this.
- virgilp 9y agoAren't cookies a web standard? I can assure you that Safari's policies w.r.t. cookies "break" a lot of website functionality, and quite intentionally so. You may not like that functionality, but the website marketers like it and have spent lots of time implementing it. So - what's ok to break, and what isn't? In the end, it's a judgement call on the browser developer. I like what another person said here - the browser is an "user agent", as long as the actions are clearly motivated by user interest, I think they're ok even if/when they break some standards.
- mcv 9y agoSo the question becomes what's less bad: for website developers to break their own site, or for Chrome to break other people's site. I'm all for empowering browsers to override abusive behaviour from websites, but using bad defaults and breaking innocent websites as a result is not the solution.
- nindalf 9y agoYou mention website developers and Chrome developers, but spare a thought for users as well. If I want to use a password manager and the website developer decided to stop me from doing that, I appreciate Chrome helping me out.
- jhasse 9y agoIts inconsistent though. I would also expect Chrome to disallow overriding the context menu for example or breaking the back button.
- CydeWeys 9y agoChrome is a program that I run on my computer. It protects my interests, not the interests of random crappy website developers doing horrible things like hijacking clipboard events. I'm all for the defaults being whatever is best for me. The browser is the agent of the user.
- gkya 9y agoHow does autocomplete=off affect password managers?
- jhasse 9y agoIt would disable the builtin password manager.
- cpeterso 9y agoPassword manager applications that are not built into the browser use clipboard pasting to insert passwords into login form fields. If browsers honored autocomplete=off, websites could block the password manager applications from entering the passwords (on their own websites).
- gkya 9y agoI don't believe password managers need autocompletion to insert passwords etc. Doesn't it only disable the completion popup?
- TheAceOfHearts 9y agoI especially hate websites that think it's ever reasonable to disable pasting into inputs! Luckily in most cases you can just right-click -> Inspect Element -> $0.value = 'paste'. You can also copy text with right-click -> Inspect Element -> copy($0.innerText). Although you'd use $0.value for an input or textarea.
- Torn 9y agoThe "don't fuck with paste" extension is worth checking out: https://chrome.google.com/webstore/detail/dont-fuck-with-paste/nkgllhigpcljnhoakjkgaieabnkmgdkb?hl=en https://chrome.google.com/webstore/detail/dont-fuck-with-pas...