Ofcourse they won't fix this. Autocomplete saves form values which are usually full of juicy information like addresses, names, ssn's, payment info, etc. which are vacuumed up by the data monster. Same with passwords. Even though the passwords themselves are encrypted it's amazing metadata to know which sites you have accounts for.
Chrome does not respect autocomplete=off (2018)
41–50 of 84 posts
Re: Chrome does not respect autocomplete=off (2018)
#42Why don't they put a flag to control this behavior in the browser? So that users who want it to be respected can actually get that?
Re: Chrome does not respect autocomplete=off (2018)
#43Earlier quoted context omitted.
I hate password forms that do this
I wish I didn’t have to disable clipboard events because of sites that think they know better to disable paste.
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)
#44(2018)
it's still active!
Re: Chrome does not respect autocomplete=off (2018)
#45Earlier quoted context omitted.
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 d…
How is expecting things to work "having an agenda?"
For the longest time Chrome would search google first before local DNS for FQDNs. When I reported that years ago they labelled it "wontfix."
In Chrome 69 they started single-sign-on and didn't get around to adding an option to disable until 71. And this autocomplete bug has been a problem for years also.
There are valid reasons to switch. I'm not here to make users feel at home. I'm here to make sure the stack runs on their machine. I find that is easier to accomplish with Firefox.
Re: Chrome does not respect autocomplete=off (2018)
#46nor should it. privacy settings should be up to user not the site.
It has nothing to do with privacy, and it may do the opposite. I’ve seen users accidentally submit forms with their phone number because we couldn’t turn off autocomplete and chrome decided something was a phone input (for no apparent reason).
If a browser wants to provide autocomplete, they should implement it in a way that is safe rather than ignoring the spec.
In this case we wanted to protect users from the mistake but couldn’t. Chrome took it upon themselves to run a basic web feature rather than implement better autocomplete.
Re: Chrome does not respect autocomplete=off (2018)
#47Earlier quoted context omitted.
I wish I didn’t have to disable clipboard events because of sites that think they know better to disable paste.
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?
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)
#48Why don't they put a flag to control this behavior in the browser? So that users who want it to be respected can actually get that?
Chrome is extremely anti user choice. They have a very "we know better than you" attitude. There is about:flags but most flags are temporary and are eventually removed.
Re: Chrome does not respect autocomplete=off (2018)
#49Cool. Do paste blockers next.
While we're complaining about pasting, am I the only one who gets annoyed by sites that only have click to copy buttons for certain content? It's often either that or they try to help me out by highlighting it. What I really want is to highlight it myself so I can paste it into my terminal. It'd be great if there was a way to get the button click copies to go to my other clipboard but I can't find anything on it anywhere
Re: Chrome does not respect autocomplete=off (2018)
#50I was asked by my users of an internal tool to disable autocomplete. I added autocomplete="off" and autocorrect="off" (spell checking makes no sense for this field), and it was disabled, including for chrome users.
Am I missing something? Is there some sort of heuristic to when it actually disables that I just got on the good side of by pure luck?