I still don't get why Chrome won't respect the password *autocomplete="off"* attribute. For fucks sake it's my goddamn website u shit brain! Obey the fucking command!!!

@AppleLover what is more painful than pre-filling a form that is not meant to prefilled

Why would you prevent it from outofilling passwords? Are you trying to force people to use weak passwords? If so, why?

Yep, I stopped using applications before because they prevented me from using them in the way I expect to use a webpage. That is, Firefox on linux (Don't fucking tell me what browser to use, there is a standard so stick to it), copy-pasting and scripting ALL inputs, browsing with or without a proxy and through a VPN, occasionally disabling JS for a faster (if uglier) experience unless I expect something interactive and not being offered push notifications before reading the third article in a row. Seriously. It won't work. Just stop.

This isn't directed at you specifically, but rather generally towards webdevs who think they know how their creations may, should and will be used..

@ArcaneEye There are lots of reasons I wouldn't want the browser to do that for me. For example my CMS where seniors creates each employee accounts via the back-end and for every account being created Chrome prefills the user password with the one from the login page... Yes I love the autocomplete feature for my login page not for my custom forms. This causes duplicated password which can in turn lead to security issues. Not all forms with passwords are login form for fucks sake. I just think that was a very poor assumption on their end.

You can follow this discussion for more rants from other devs requesting they drop the shitty buggy feature. https://groups.google.com/a/...