News for hackers. Stuff that matters.
Re:Chrome does not respect autocomplete=off (2018) by fshbbdssbbgdd on Monday March 01, 2021 @07:05PM (#26310255)
Thanks, Chrome. So many sites have user-hostile code that is overridden by this choice. I still remember the glee when I first started using Chrome all those years ago, and suddenly all those forms filled themselves out.
Re:Chrome does not respect autocomplete=off (2018) by eli on Monday March 01, 2021 @07:20PM (#26310364)
I’ve seen autocomplete create plenty of problems. It can break some (admittedly poorly designed) forms outright. Or in others simply create a bad user experience. There are lots of forms that ask for an address but that should never be autocompleted to the user’s address.

In practice as a developer you have to resort to JavaScript hacks and obfuscating form field names to avoid it.

Re:Chrome does not respect autocomplete=off (2018) by ehsankia on Monday March 01, 2021 @07:46PM (#26310538)
I really really wish there was a way (holding shift, ctrl or something) to only autofill the one field without it goig to fill/replace every other field on the page. It's so annoying when the stuff you just field get replaced just because you want to autofill one field.
Re:Chrome does not respect autocomplete=off (2018) by stefan_ on Monday March 01, 2021 @07:50PM (#26310563)
My favorite is when it autofills a whole form that has the field name only as a hint that disappears once it's filled. Of course it always fills with the wrong set of information.
Re:Chrome does not respect autocomplete=off (2018) by exporectomy on Monday March 01, 2021 @08:56PM (#26311014)
That sound's like the form's fault. Even filling it in manually, you won't be able to double-check that you entered the right information.
Re:Chrome does not respect autocomplete=off (2018) by rectang on Monday March 01, 2021 @07:56PM (#26310600)
I typically type everything manually in long forms because the autofill tends to get something wrong every once in a while. It's like choosing to drive the car myself rather than trusting the self-driving feature.

I figure most people just tolerate wrong inputs and live with the results. (It doesn't happen that often.)

Re:Chrome does not respect autocomplete=off (2018) by jessriedel on Monday March 01, 2021 @08:48PM (#26310966)
:/

> It's very hackish way but I found a trick to achieve the same.

> So you should go to chrome://settings/addresses?search=address

> Now create multiple addresses, each with only one field filled. So one should only have your E-Mail, another record should contain only your first name only, and so on.

https://superuser.com/questions/477144/can-autofill-in-chrom...

A variation:

https://support.google.com/chrome/thread/31845659?hl=en

Re:Chrome does not respect autocomplete=off (2018) by larzang on Monday March 01, 2021 @07:34PM (#26310464)
Having worked on a number of CRM and other business applications, yep, it's maddening. Not all addresses and names are your address and name.
Re:Chrome does not respect autocomplete=off (2018) by wongarsu on Monday March 01, 2021 @07:32PM (#26310445)
But any new code that's being written just finds other ways to avoid autocomplete. Ignoring autocomplete=off makes the web a bit less standards compliant for a a very short temporary benefit.
Re:Chrome does not respect autocomplete=off (2018) by wrwatson on Monday March 01, 2021 @07:55PM (#26310592)
I'm the developer of a Virtual Terminal web page which allows a merchant to accept credit card payments. I would love to turn-off autocomplete for the credit card details. The person using the Virtual Terminal wants to type in someone else's card number, not use their own every time.

The PCI-DSS council is partly to blame here, for recommending autocomplete=off in other contexts.

Re:Chrome does not respect autocomplete=off (2018) by colejohnson66 on Monday March 01, 2021 @07:13PM (#26310319)
I hate password forms that do this
Re:Chrome does not respect autocomplete=off (2018) by Spivak on Monday March 01, 2021 @07:22PM (#26310379)
I wish I didn’t have to disable clipboard events because of sites that think they know better to disable paste.
Re:Chrome does not respect autocomplete=off (2018) by rangibaby on Monday March 01, 2021 @08:08PM (#26310689)
Why do they even do that? What’s so bad about pasting into a form? Does the person who designed the form think your password isn’t secure unless it is written on a piece of paper kept in a bank vault?
Re:Chrome does not respect autocomplete=off (2018) by mod on Monday March 01, 2021 @08:15PM (#26310744)
Especially when I'm pasting my routing number or bank account number.

Like are you kidding me? I went into my bank app/website, I used the "copy" feature, and I'm trying to paste here AND into your "confirmation" field. Because I don't want to typo it!

How could my copy skill be worse than my typing skill?

Re:Chrome does not respect autocomplete=off (2018) by exporectomy on Monday March 01, 2021 @09:05PM (#26311080)
I'm on board with not allowing paste into a confirmation field since you might have copied the wrong number so there's nothing to gain from confirming the same mistake. Imagine you're doing several transactions and on one of them, you don't quite press the copy key correctly and end up using the previous account number from the clipboard.
Re:Chrome does not respect autocomplete=off (2018) by city41 on Monday March 01, 2021 @09:15PM (#26311165)
Curious how you disable clipboard events? I always go into the dev console and do $0.value = '<my password>'