Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome does not respect autocomplete=off (2018)

bugs.chromium.org

Post reply on HN
Print view View original

31–40 of 84 posts

Re: Chrome does not respect autocomplete=off (2018)

#31

Post by twistedpair »

martinmunk wrote: post #20

I’m not sure, but this might be related to my issues whenever I used chrome, and it would auto fill hidden elements of settings forms in pfSense. All of a sudden you had changed stuff you didn’t mean to, or get seemingly weird errors about invalid input. At least I could imagine this prop being applied to hidden elements, either in pfSense or internally in chrome.

I took our CI/CD pipelines offline when I edited one form in the CI/CD users admin panel, and Chrome autocompleted a hidden form, disabling various permissions. :/

Re: Chrome does not respect autocomplete=off (2018)

#32

Post by stefan_ »

ehsankia wrote: post #29
eli wrote: post #12

Earlier quoted context omitted.

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.

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.

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)

#33

Post by kelnos »

meibo wrote: post #30
zelon88 wrote: post #18

It is ironic that so many developers are taking the time to complain on the bug tracker but won't simply write Chrome out of their org. I did that at a place and most of the users didn't even realize something had changed. No developers seem to have a problem simply refusing to support Firefox. I wonder how much extra effort it is going to take for them to finally make the switch.

Maybe you haven't checked this since 2013: https://gs.statcounter.com/browser-market-share This statistic is not without reason. Chrome still has considerable usability and security advantages, especially for non-technical people(at least on anything that's not OS X), and still the best dev tools out there. We can be lucky that FF at least tries to stick to standards where Safari doesn't bother.

I don't think that's material. If we're talking about corporate policy on corporate-owned machines, employees shouldn't be complaining to IT that their favorite websites aren't working properly in Firefox. If they do, the canned IT response should always be "why are you doing personal tasks on your work machine?"

As long as the corporate/enterprise apps work on Firefox (which they should?), it's not a problem for a corporate IT department to ban Chrome.

Re: Chrome does not respect autocomplete=off (2018)

#35

Post by wrwatson »

fshbbdssbbgdd wrote: post #4

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.

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)

#36

Post by rectang »

ehsankia wrote: post #29
eli wrote: post #12

Earlier quoted context omitted.

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.

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.

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)

#37

Post by kelnos »

chovybizzass wrote: post #3

nor should it. privacy settings should be up to user not the site.

I think the purpose of autocomplete="off" is to allow an (honest, well-meaning) web site to tell a browser, "I know you think this looks like an address field, but it really isn't".

Unfortunately, in reality, it's probably more often used to force users to type things in for misguided "security reasons".

I think browser UI for this is generally just bad. I think forms should never auto-fill, but when I click on a form field, it should give me a dropdown to select text to put in just that field. Not that field plus all other fields in the form. Just that field. Then you don't have privacy issues (because the site never sees the autocomplete options unless the user actively selects one), and autocomplete="off" becomes unnecessary.

Re: Chrome does not respect autocomplete=off (2018)

#38

Post by MattGaiser »

kelnos wrote: post #33
meibo wrote: post #30

Earlier quoted context omitted.

Maybe you haven't checked this since 2013: https://gs.statcounter.com/browser-market-share This statistic is not without reason. Chrome still has considerable usability and security advantages, especially for non-technical people(at least on anything that's not OS X), and still the best dev tools out there. We can be lucky that FF at least tries to stick to standards where Safari doesn't bother.

I don't think that's material. If we're talking about corporate policy on corporate-owned machines, employees shouldn't be complaining to IT that their favorite websites aren't working properly in Firefox. If they do, the canned IT response should always be "why are you doing personal tasks on your work machine?" As long as the corporate/enterprise apps work on Firefox (which they should?), it's not a problem for a c…

> As long as the corporate/enterprise apps work on Firefox (which they should?)

They have even less of a reason to support Firefox. I used to work on an partially enterprise (well, government) program. We dropped Firefox support for it because it was easier to tell the client to just install Chrome. And the complexity of enterprise software means that that will always be easier for the client as well than switching.

Re: Chrome does not respect autocomplete=off (2018)

#40

Post by meibo »

kelnos wrote: post #33
meibo wrote: post #30

Earlier quoted context omitted.

Maybe you haven't checked this since 2013: https://gs.statcounter.com/browser-market-share This statistic is not without reason. Chrome still has considerable usability and security advantages, especially for non-technical people(at least on anything that's not OS X), and still the best dev tools out there. We can be lucky that FF at least tries to stick to standards where Safari doesn't bother.

I don't think that's material. If we're talking about corporate policy on corporate-owned machines, employees shouldn't be complaining to IT that their favorite websites aren't working properly in Firefox. If they do, the canned IT response should always be "why are you doing personal tasks on your work machine?" As long as the corporate/enterprise apps work on Firefox (which they should?), it's not a problem for a c…

Companies also want their employees to be as productive as possible, which are likely already using Chrome at home because it has the best usability and quality of life for non-technical users.

I don't think any IT department worth their while would ban worthwhile software because of some agenda that frankly just doesn't matter too much to most regular users, at least in an US context.

In the EU this might be a bit different, as they would have an interest in getting Google out of their ecosystems - but we've seen that that just doesn't really work too well, with pilots in various governments. People aren't as productive and complain about not having the same Excel and the same Internet as they have at home.

Post reply on HN