I stumbled across this issue because I had the same problem. Not in React, but the problem is universal. Maybe this will help anyone else who stumbles upon this. None of the other answers actually answer the problem. The problem as described by the OP is that Chrome doesn’t set the value of the inputs … Read more
Currently there is no direct way to disable the autofill for an entire application, since the autofill feature is View specific. You can still try this way and call BaseActivity everywhere. public class BaseActivity extends AppCompatActivity { @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); disableAutofill(); } @TargetApi(Build.VERSION_CODES.O) private void disableAutofill() { getWindow().getDecorView().setImportantForAutofill(View.IMPORTANT_FOR_AUTOFILL_NO_EXCLUDE_DESCENDANTS); } } You … Read more
For firefox Either: <asp:TextBox id=”Textbox1″ runat=”server” autocomplete=”off”></asp:TextBox> Or from the CodeBehind: Textbox1.Attributes.Add(“autocomplete”, “off”);
going to settings of the simulator -> Passwords -> Turn On and then Turn OFF AutoFill passwords. type any password
Here’s the magic you want: autocomplete=”new-password” Chrome intentionally ignores autocomplete=”off” and autocomplete=”false”. However, they put new-password in as a special clause to stop new password forms from being auto-filled. I put the above line in my password input, and now I can edit other fields in my form and the password is not auto-filled.
The OP’s problem may have been solved (or may have come back again in recent updates!) but as of early 2019, you can diagnose some of these problems by setting the show-autofill-type-predictions flag in chrome://flags, restarting Chrome, then looking at the title (tooltip text) for the input in question. It will tell you what information … Read more
The reason browsers are ignoring autocomplete=off is because there have been some web-sites that tried to disable auto-completing of passwords. That is wrong. And in July 2014 Firefox was the last major browser to finally implement the change to ignore any web-site that tries to turn off autocompleting of passwords. June 2009: IEInternals blog where … Read more
Trick it with a “strong” inside shadow: input:-webkit-autofill { -webkit-box-shadow:0 0 0 50px white inset; /* Change the color to your own background color */ -webkit-text-fill-color: #333; } input:-webkit-autofill:focus { -webkit-box-shadow: 0 0 0 50px white inset;/*your box-shadow*/ -webkit-text-fill-color: #333; }
UPDATE for 2017: Looks like the answer from Katie has more up-to-date information than mine. Future readers: give your up-votes to her answer. This is a great question and one for which documentation is surprisingly hard to come by. Actually, in many cases you will find that the Chrome Autofill functionality “just works.” For example, … Read more
The problem is autofill is handled differently by different browsers. Some dispatch the change event, some don’t. So it is almost impossible to hook onto an event which is triggered when browser autocompletes an input field. Change event trigger for different browsers: For username/password fields: Firefox 4, IE 7, and IE 8 don’t dispatch the … Read more