So far this combinations seems to be working for me
role="combobox" autocomplete="off"
Issue 914451: Autofill does not respect autocomplete="off"
351–360 of 383 posts
Re: Issue 914451: Autofill does not respect autocomplete="off"
#352If you look at the chrome sources you can find this flag:
const char kAutofillOffNoServerDataDescription[] = "Disables Autofill for fields with autocomplete off that have no " "crowd-sourced evidence that Autofill would be helpful.";
So, at least in a company, this should work to avoid autocomplete making corporate apps unusable.
another thing that seems to work for me, is adding role="combobox" along with autocomplete="off"
Re: Issue 914451: Autofill does not respect autocomplete="off"
#353Earlier quoted context omitted.
This has a lot of really serious implications. I built a form for a charity that allowed users to buy a subscription but include an additional donation amount. Chrome was sometimes filling that field with the two-digit year. The charity got a lot of complaints and it ruined the trust relationship with the donors who didn't understand what was happening and thought it was intentional.
Chrome has other behaviour that I think violates a sort of trust relationship. One of which is that Youtube would ask you "do you want to install Chrome"? Almost as if your current browser is not "what you need to access Youtube". This is especially a problem for elderly people who often use the web but don't really understand how things fit together (the way 5 year olds actually do).
[deleted]
Re: Issue 914451: Autofill does not respect autocomplete="off"
#354Earlier quoted context omitted.
We're not talking about choice for users . This is about choice for developers .
Likewise I had Netscape, Opera, IE on my development environment.
Are you being deliberately obtuse? Choice of which browsers to develop for. You had to support IE6 back in the day. Now you have to support Chrome. When they do weird shit you can't say "well that browser is broken", you have to work around it.
Surely most people here are old enough to remember the days of IE6? It wasn't that long ago.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#355Because other people here are throwing in their frustrations, I will at least add that on the flip side I have been frustrated by sites that attempt to disable autofill for illegitimate reasons, like attempting to disallow password managers. I think I understand where this is coming from. On the other hand, I, too, have been bit by this at least once, in the past. I think it was easier to just disable it at that time…
Chrome explains in their security FAQ [0] why they don't adhere to autocomplete=off for password fields. They could still follow it for other fields. 0: https://chromium.googlesource.com/chromium/src/+/master/docs...
Shouldn't the work on changing the spec, rather then confusing majority of developers and causing even financial loss and embarrassment for many? This thread is filled with cases where this caused issues.
Google should spend their cycles to work on a standard for password managers. The current design of those is flawed anyway.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#356I ran into this last week (with LastPass, not Chrome - this seems to be a common practice): I have a form where users enter information about their suppliers (I make restaurant management software). This includes a field for the contact email address, which LastPass was autofilling the email address the user used to log in. This happened silently, quickly enough that users wouldn't notice it on page transition, and w…
The LastPass on is especially horrific because it fills in fields that are already filled, and it fires a change event . So if you're auto-saving on a change event, that data is lost as soon as the page is loaded.
The entire design of password managers that hijacking the DOM is flawed.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#357As I had already commented on the issue, it completely breaks Germany's main train ticket selling website: https://i.imgur.com/BjYTgSn.png They have tagged the field as autocomplete=off but Chrome just doesn't care. Also see this linked issue where they collected valid use cases for autocomplete=off. They just seem to ignore 452 use cases (I can't comment on the quality of them, I did not read any). https://bugs.chro…
Finally i know why this happens only in Chromium. This irritates me for quite some time now... Seems that Chromium based browsers aren't favorable any more: Tracking, Bugs, uBlock extension is flagged, Manifestv3, etc. But Firefox has the same problem since it ships with Pocket and other sync stuff. I know that they really do care but they have problems of their own which really make me think which browser to use. Th…
I use Firefox as my main browser on all my machines and haven't once been bothered about Pocket or other sync stuff. I vastly prefer it, for moral and technical reasons. I feared the switch from Chrome would be very hard and aggravating but it wasn't.
(The only thing that got me the first few weeks is that opening an incognito window is ctrl+shift+p instead of ctrl+shift+n. Once I got used to that I realized it actually makes sense because ctrl+shift+n re-opens a closed window just like ctrl+shift+t reopens a closed tab.)
Re: Issue 914451: Autofill does not respect autocomplete="off"
#358Re: Issue 914451: Autofill does not respect autocomplete="off"
#359I hat to fight with browser autocomplete in Kibana main search bar.
On the other hand I guess it is the same as right mouse button - I don't allow any site to capture that event since some abuse it.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#360Earlier quoted context omitted.
I think we need a way to disable features only for those developers that abuse them. Like uMatrix but built-in and with rules being supplied automatically as ad blocking lists are. You autocomplete=off a password field? That attribute won't have an effect on your site anymore. You auto-play videos when the user doesn't expect it? What videos? The web doesn't support videos – as far as you are concerned. Scroll hijack…
Can we have a reliable cross-browser way to say "this is a change password field, so don't autocomplete it" and "this is an email address field not a username field, so don't autocomplete it with the login username"?
Developers can say that. What we need is a reliable way to know if they're lying.