Chrome ignores autocomplete off

Question

I ve created a web application which uses a tagbox drop down  This works great in all browsers except Chrome browser  Version 21 0 1180 89    Despite both the input fields AND the form field having the autocomplete  off  attribute  Chrome insists on showing a drop down history of previous entries for the field  which is obliterating the tagbox list

User · Answer

I had the similar issue with one of the search field in my form. neither autocomplete= "false" nor autocomplete= "off" worked for me. turns out when you have aria-label attribute in the input element is set to something like city or address or something similar , chrome overrides all your settings and display the autocomplete anyway

So fix i have done is to remove the city part from the aria-label and come up with a different value. and finally autocomplete stopped showing

User · Answer

After the chrome v  34  setting autocomplete  off  at  lt form gt  tag doesn t work  I made the changes to avoid this annoying behavior    Remove the name and the id of the password input Put a class in the input  ex   passwordInput      So far  Chrome wont put the saved password on the input  but the form is now broken   Finally  to make the form work  put this code to run when the user click the submit button  or whenever you want to trigger the form submittion   var sI       passwordInput   0     sI  attr  id    password      sI  attr  name    password      In my case  I used to hav id  password  name  password  in the password input  so I put them back before trigger the submition

User · Answer

I solved in another way  You can try this    lt input id  passfld  type  text  autocomplete  off    gt   lt script type  text javascript  gt     Using jQuery   function                                                       setTimeout function               input passfld   attr  type   password          10            or in pure javascript  window onload function                                                      setTimeout function              document getElementById  passfld   type    password         10           lt  script gt

User · Answer

I am using Chrome - Version 64 0 3282 140  Official Build   64-bit  and used following code along with form name and it works for me    lt form name  formNameHere  gt      lt  form gt   lt script type  text javascript  gt      setTimeout function            document formNameHere reset          500    lt  script gt

User · Answer

In Chrome 48  use this solution    Put fake fields before real fields    lt form autocomplete  off  gt     lt input name  fake email     class  visually-hidden  type  text  gt     lt input name  fake password  class  visually-hidden  type  password  gt      lt input autocomplete  off  name  email     type  text  gt     lt input autocomplete  off  name  password  type  password  gt   lt  form gt   Hide fake fields    visually-hidden     margin  -1px    padding  0    width  1px    height  1px    overflow  hidden    clip  rect 0 0 0 0     clip  rect 0  0  0  0     position  absolute     You did it    Also this will work for older versions

User · Answer

I am posting this answer to bring an updated solution to this problem  I am currently using Chrome 49 and no given answer work for this one  I am also looking for a solution working with other browsers and previous versions   Put this code on the beginning of your form   lt div style  display  none   gt       lt input type  text  autocomplete  new-password  gt       lt input type  password  autocomplete  new-password  gt   lt  div gt    Then  for your real password field  use   lt input type  password  name  password  autocomplete  new-password  gt    Comment this answer if this is no longer working or if you get an issue with another browser or version   Approved on    Chrome   49 Firefox   44  45 Edge   25 Internet Explorer   11

User · Answer

UPDATE  It seems now Chrome ignores the style  display  none   or style  visibility  hidden  attributes   You can change it to something like    lt input style  opacity  0 position  absolute   gt   lt input type  password  style  opacity  0 position  absolute   gt    In my experience  Chrome only autocompletes the first  lt input type  password  gt  and the previous  lt input gt   So I ve added    lt input style  display none  gt   lt input type  password  style  display none  gt    To the top of the  lt form gt  and the case was resolved

User · Answer

autocomplete  off  is usually working  but not always  It depends on the name of the input field  Names like  address    email    name  - will be autocompleted  browsers think they help users   when fields like  code    pin  - will not be autocompleted  if autocomplete  off  is set   My problems was - autocomplete was messing with google address helper  I fixed it by renaming it   from    lt input type  text  name  address  autocomplete  off  gt    to   lt input type  text  name  the address  autocomplete  off  gt    Tested in chrome 71

User · Answer

The solution at present is to use type  search   Google doesn t apply autofill to inputs with a type of search   See  https   twitter com Paul Kinlan status 596613148985171968  Update 04 04 2016  Looks like this is fixed  See http   codereview chromium org 1473733008

User · Answer

I ve solved the endless fight with Google Chrome with the use of random characters  When you always render autocomplete with random string  it will never remember anything    lt input name  name  type  text  autocomplete  rutjfkde  gt    Hope that it will help to other people

User · Answer

Instead of autocomplete  off  use autocomplete  false      from  https   stackoverflow com a 29582380 75799

User · Answer

For me setting autocomplete  quot off quot  in form and inputs worked  But can be flake  Some times it will suggest password or some saved login password option  But don t come pre-filled  Chrome Version  81 0 4044 138 CodePen  x000D   x000D   lt form role  form  method  post  action     autocomplete  off  gt     lt label for  login  gt Login lt  label gt  lt br  gt     lt input type  text  name  login  id  login  autocomplete  off    gt     lt br  gt  lt br  gt     lt label for  password  gt Password lt  label gt  lt br  gt     lt input type  password  name  password  autocomplete  off    gt     lt br  gt  lt br  gt     lt input type  submit  name  submit  value  Submit    gt   lt  form gt  x000D   x000D   x000D   Others Options   Remove  form  tag    or changing it from  div  to  form  before submitting  With javascript and some contentEditable  quot true quot  fields could make your way     Usually I have to find another work around every few months

User · Answer

Whilst I agree autocomplete should be a user choice  there are times when Chrome is over-zealous with it  other browsers may be too   For instance  a password field with a different name is still auto-filled with a saved password and the previous field populated with the username  This particularly sucks when the form is a user management form for a web app and you don t want autofill to populate it with your own credentials   Chrome completely ignores autocomplete  off  now  Whilst the JS hacks may well work  I found a simple way which works at the time of writing   Set the value of the password field to the control character 8    x08  in PHP or  amp  8  in HTML   This stops Chrome auto-filling the field because it has a value  but no actual value is entered because this is the backspace character   Yes this is still a hack  but it works for me  YMMV

User · Answer

After having tried all solutions  Here is what seems to be working for chrome version 45  with form having password field     jQuery  document   ready function              For disabling Chrome Autocomplete         jQuery    text    attr  autocomplete   pre  Math random 0 100000000

User · Answer

Chrome keeps changing the way it handles autocomplete on each version  the way I came up was  to make the fields readonly and onclick focus make it Not readonly  try this jQuery snippet  jQuery document  ready function             fix for autocomplete    input   input   attr  readonly  true    readonly all inputs on page load  prevent autofilling on pageload      input   input   on   click focus   function      on input click     input   input   attr  readonly  true    make other fields readonly     this   attr  readonly  false    but make this field Not readonly                fix for autocomplete

User · Answer

autocomplete off is largely ignored in modern browsers - primarily due to password managers etc   You can try adding this autocomplete  new-password  it s not fully supported by all browsers  but it works on some

User · Answer

Writing a 2020 answer in case if this helps anyone  I tried many combinations above  though there is one key that was missed in my case  Even though I had kept autocomplete  quot nope quot  a random string  it didn t work for me because I had name attribute missing  so I kept name  password  and autocomplete    quot new-password quot  for username  I kept name  quot usrid quot     DONT KEEP STRING THAT CONTAINS  user  and autocomplete    quot new-password quot     Same for it as well  so google stops suggesting password  manage password dropdown  this worked very well for me   I did this for Android and iOS web view that Cordova ionic uses   lt ion-input  type   quot passwordType quot  name  quot password quot  class  quot input-form-placeholder quot  formControlName  quot model password quot          autocomplete  quot new-password quot   clearInput   quot showClearInputIconForPassword quot  gt   lt  ion-input gt

User · Answer

You can use below concept to implement AutoComplete  false  for chrome as well as others browser   lt input style  quot opacity  0  position  absolute  z-index  -1  quot  name  quot email quot  gt   lt input type  quot search quot  name  quot email quot  class  quot form-control quot  autocomplete  quot new-email quot  id  quot email quot  gt

User · Answer

The hidden input element trick still appears to work  Chrome 43  to prevent autofill  but one thing to keep in mind is that Chrome will attempt to autofill based on the placeholder tag  You need to match the hidden input element s placeholder to that of the input you re trying to disable   In my case  I had a field with a placeholder text of  City or Zip  which I was using with Google Place Autocomplete  It appeared that it was attempting to autofill as if it were part of an address form  The trick didn t work until I put the same placeholder on the hidden element as on the real input    lt input style  display none   type  text  placeholder  City or Zip    gt   lt input autocomplete  off  type  text  placeholder  City or Zip    gt

User · Answer

After lot of digging I found that autocomplete dropdown on Chrome Version 83 0 4103 116  doesn t shows up when we remove name and id attribute on input tag eg  code as below  x000D   x000D   lt div gt   lt span gt    Auto complete off works if name and id attribute is not set on input tag     lt input type  text   gt   lt  span gt   lt span gt    Auto complete will work here since id attribute is set    lt input id  name  type  text   gt   lt  span gt   lt  div gt  x000D   x000D   x000D

User · Answer

i found this solution to be the most appropriate    function clearChromeAutocomplete        not possible  let s try   if  navigator userAgent toLowerCase   indexOf  chrome    gt   0     document getElementById  adminForm   setAttribute  autocomplete    off     setTimeout function              document getElementById  adminForm   setAttribute  autocomplete    on        1500         It must be loaded after dom ready  or after the form renders

User · Answer

Up until just this last week  the two solutions below appeared to work for Chrome  IE and Firefox  But with the release of Chrome version 48  and still in 49   they no longer work    The following at the top of the form        lt input style  display none  type  text  name  fakeUsername   gt   lt input style  display none  type  password  name  fakePassword   gt     The following in the password input element   autocomplete  off    So to quickly fix this  at first I tried to use a major hack of initially setting the password input element to disabled and then used a setTimeout in the document ready function to enable it again    setTimeout function       PasswordData   prop  disabled   false     50     But this seemed so crazy and I did some more searching and found  tibalts answer in Disabling Chrome Autofill  His answer is to use autocomplete  new-password  in the passwords input and this appears to work on all browsers  I have kept my fix number 1 above at this stage    Here is the link in the Google Chrome developer discussion  https   code google com p chromium issues detail id 370363 c7

User · Answer

I ve found another solution - just mask the characters in your autocomplete  quot off quot  inputs with style  quot -webkit-text-security  disc  quot   You can also add it to your CSS rules in something like following way   autocomplete  quot off quot       -webkit-text-security  disc     The main goal is to elminate the type  quot password quot  or other simillar type attribute from the element  At least  for the moment of 2021-01-24 this solution works

User · Answer

Prevent autocomplete of username  or email  and password     lt input type  email  name  email  gt  lt  -- Can be type  text  -- gt   lt input type  password  name  password  autocomplete  new-password  gt      Prevent autocomplete a field  might not work     lt input type  text  name  field  autocomplete  nope  gt    Explanation   autocomplete still works on an  lt input gt despite having autocomplete  off   but you can change off to a random string  like nope     Others  solutions  for disabling the autocomplete of a field  it s not the right way to do it  but it works    1   HTML    lt input type  password  id  some id  autocomplete  new-password  gt    JS  onload     function         var some id   document getElementById  some id        some id type    text       some id removeAttribute  autocomplete            or using jQuery     document  ready function         var some id       some id        some id prop  type    text        some id removeAttr  autocomplete            2   HTML    lt form id  form  gt  lt  form gt    JS  onload     function         var input   document createElement  INPUT        input type    text       document getElementById  form   appendChild input           or using jQuery     document  ready function             lt input gt              type   text         appendTo     form             To add more than one field using jQuery    x000D   x000D  function addField label    x000D    var div       lt div gt     x000D    var input       lt input gt      x000D      type   text  x000D        x000D     x000D    if label    x000D      var label       lt label gt      x000D        text  label x000D          x000D       x000D      label append input   x000D      div append label       x000D      else   x000D      div append input       x000D        x000D     x000D    div appendTo     form     x000D    x000D   x000D    document  ready function     x000D    addField    x000D    addField  Field 1        x000D      x000D   lt script src  https   ajax googleapis com ajax libs jquery 2 1 1 jquery min js  gt  lt  script gt  x000D   lt form id  form  gt  lt  form gt  x000D   x000D   x000D      Works in    Chrome  49  Firefox  44

User · Answer

Add this right after form tag    lt form gt   lt div class  div-form  gt   lt input type  text  gt   lt input type  password   gt   lt  div gt    Add this to your css file    div-form  opacity  0

User · Answer

To prevent autocomplete  just set an empty space as the input value    lt input type  text  name  name  value      gt

User · Answer

As of Chrome 42  none of the solutions hacks in this thread  as of 2015-05-21T12 50 23 00 00  work for disabling autocomplete for an individual field or the entire form    EDIT  I ve found that you actually only need to insert one dummy email field into your form  you can hide it with display  none  before the other fields to prevent autocompleting  I presume that chrome stores some sort of form signature with each autocompleted field and including another email field corrupts this signature and prevents autocompleting    lt form action   login  method  post  gt       lt input type  email  name  fake email  style  display none  aria-hidden  true  gt       lt input type  email  name  email  gt       lt input type  password  name  password  gt       lt input type  submit  gt   lt  form gt    The good news is that since the  form signature  is corrupted by this  none of the fields are autocompleted  so no JS is needed to clear the fake fields before submission   Old Answer   The only thing I ve found to be still viable is to insert two dummy fields of type email and password before the real fields  You can set them to display  none to hide them away  it isn t smart enough to ignore those fields     lt form action   login  method  post  gt       lt input type  email  name  fake email  style  display none  aria-hidden  true  gt       lt input type  password  name  fake password  style  display none  aria-hidden  true  gt       lt input type  email  name  email  gt       lt input type  password  name  password  gt       lt input type  submit  gt   lt  form gt    Unfortunately  the fields must be within your form  otherwise both sets of inputs are autofilled   So  for the fake fields to be truly ignored you ll need some JS to run on form submit to clear them   form addEventListener  submit   function         form elements  fake email   value           form elements  fake password   value               Notice from above that clearing the value with Javascript works to override the autocomplete  So if loosing the proper behavior with JS disabled is acceptable  you can simplify all of this with a JS autocomplete  polyfill  for Chrome    function document         function polyfillAutocomplete nodes             for var i   0  length   nodes length  i  lt  length  i                   if nodes i  getAttribute  autocomplete        off                      nodes i  value                                          setTimeout function              polyfillAutocomplete document getElementsByTagName  input             polyfillAutocomplete document getElementsByTagName  textarea             1       window document

User · Answer

It appears that Chrome now ignores autocomplete  off  unless it is on the  lt form autocomplete  off  gt  tag

User · Answer

I ve came up with the following solution that queries all fields with the attribute autocomple  off  then set it s value to a single space then set a timer for around 200ms and set the value back to an empty string   Example      hack to prevent auto fill on chrome var noFill   document querySelectorAll  input autocomplete off      noFill forEach function el        el setAttribute  value             setTimeout function             el setAttribute  value               200         I choose 200ms for the timer because after some experimentation 200ms seems to be the amount of time it takes on my computer for chrome to give up on trying to autocomplete the fields  I m welcome to hear what other times seem to work better for other people

User · Answer

Seen chrome ignore the autocomplete  off   I solve it with a stupid way which is using  fake input  to cheat chrome to fill it up instead of filling the  real  one   Example    lt input type  text  name  username  style  display none  value  fake input    gt    lt input type  text  name  username  value  real input   gt    Chrome will fill up the  fake input   and when submit  server will take the  real input  value

User · Answer

Looks like this is fixed  See https   codereview chromium org 1473733008

User · Answer

For this problem I have used this css solution  It is working for me   input    text-security disc  important    -webkit-text-security disc  important    -moz-text-security disc  important

User · Answer

When using a widget like jQuery UI s Autocomplete make sure to check that it is not adding changing to autocomplete attribute to off  I found this to be true when using it and will break any work you may have done to override any browser field caching  Make certain that you have a unique name attribute and force a unique autocomplete attribute after the widget initializes  See below for some hints on how that might work for your situation    lt  php  autocomplete    off   time      gt   lt script gt         email   autocomplete         create  function  event  ui                this  attr  autocomplete    lt   echo  autocomplete    gt                    source  function  request  response      your code here          focus  function  event  ui       your code here          select  function  event  ui       your code here            lt  script gt   lt input type  email  id  email  name  email  lt   echo  autocomplete    gt   autocomplete   lt   echo  autocomplete    gt     gt

User · Answer

No clue why this worked in my case  but on chrome I used autocomplete  none  and Chrome stopped suggesting addresses for my text field

User · Answer

2021 UPDATE  change  lt input type  quot text quot  gt  to  lt input type  quot search quot  gt  That is all  Keeping the below answer around for nostalgia  For a reliable workaround  you can add this code to your layout page   lt div style  quot display  none  quot  gt    lt input type  quot text quot  id  quot PreventChromeAutocomplete quot     name  quot PreventChromeAutocomplete quot  autocomplete  quot address-level4 quot    gt   lt  div gt   Chrome respects autocomplete off only when there is at least one other input element in the form with any other autocomplete value  This will not work with password fields--those are handled very differently in Chrome  See https   code google com p chromium issues detail id 468153 for more details  UPDATE  Bug closed as  quot Won t Fix quot  by Chromium Team March 11  2016  See last comment in my originally filed bug report  for full explanation  TL DR  use semantic autocomplete attributes such as autocomplete  quot new-street-address quot  to avoid Chrome performing autofill

User · Answer

Autocomplete  Off  doesn t work anymore    Try using just a random string instead of  Off   for example Autocomplete  NoAutocomplete   I hope it helps

User · Answer

Browser does not care about autocomplete off auto or even fills credentials to wrong text field   I fixed it by setting the password field to read-only and activate it  when user clicks into it or uses tab-key to this field   fix browser autofill in  readonly and set writeble on focus  at mouse click and tabbing through fields     lt input type  password  readonly        onfocus    this  removeAttr  readonly      gt    Update  Mobile Safari sets cursor in the field  but does not show virtual keyboard  New Fix works like before but handles virtual keyboard    lt input id  email  readonly type  email  onfocus  if  this hasAttribute  readonly          this removeAttribute  readonly           fix for mobile safari to show virtual keyboard     this blur       this focus          gt    Live Demo https   jsfiddle net danielsuess n0scguv6      UpdateEnd  By the way  more information on my observation   Sometimes I notice this strange behavior on Chrome and Safari  when there are password fields in the same form  I guess  the browser looks for a password field to insert your saved credentials  Then it autofills username into the nearest textlike-input field   that appears prior the password field in DOM  just guessing due to observation   As the browser is the last instance and you can not control it  sometimes even autocomplete off would not prevent to fill in credentials into wrong fields  but not user or nickname field

User · Answer

to anyone looking for a solution to this  I finally figure it out    Chrome only obey s the autocomplete  off  if the page is a HTML5 page  I was using XHTML    I converted my page to HTML5 and the problem went away  facepalm

User · Answer

Change input type attribute to type  search     Google doesn t apply auto-fill to inputs with a type of search

User · Answer

Modern Approach  Simply make your input readonly  and on focus  remove it  This is a very simple approach and browsers will not populate readonly inputs  Therefore  this method is accepted and will never be overwritten by future browser updates    lt input type  text  onfocus  this removeAttribute  readonly     readonly   gt    The next part is optional  Style your input accordingly so that it does not look like a readonly input   input readonly         cursor  text       background-color   fff      WORKING EXAMPLE

User · Answer

I ve just tried the following  and it appears to do the trick on Chrome 53 - it also disables the  Use password for   drop down when entering the password field   Simply set your password input type to text  and then add the onfocus handler  inline or via jQuery vanilla JS  to set the type to password     onfocus  this setAttribute  type   password      Or even better   onfocus  if this getAttribute  type      text   this setAttribute  type   password

User · Answer

Some end 2020 Update  I tried all the old solutions from different sites  None of them worked   -  Then I found this  Use  lt input type  quot search quot   gt    and the autocomplete is gone  Success with Chrome 86  FireFox  Edge 87

User · Answer

I have a nearly perfect solution for this issue  Remove  type password  from all password input elements after all of them were loaded into DOM give a timeout to set the  type password  back Chrome will ignore  the changed type for auto filling Example   setTimeout     gt  ele type  password   3000    Or change the type by event   ele oninput function   ele type  password

User · Answer

Chrome version 34 now ignores the autocomplete off   see this   Lots of discussion on whether this is a good thing or a bad thing  Whats your views

User · Answer

I just updated to Chrome 49 and Diogo Cid s solution doesn t work anymore   I made a different workaround hiding and removing the fields at run-time after the page is loaded   Chrome now ignores the original workaround applying the credentials to the first displayed type  password  field and its previous type  text  field  so I have hidden both fields using CSS visibility  hidden    lt  -- HTML -- gt   lt form gt       lt  -- Fake fields -- gt       lt input class  chromeHack-autocomplete  gt       lt input type  password  class  chromeHack-autocomplete  gt        lt input type  text  placeholder  e-mail  autocomplete  off    gt       lt input type  password  placeholder  Password  autocomplete  off    gt   lt  form gt    lt  -- CSS -- gt   chromeHack-autocomplete       height  0px  important      width  0px  important      opacity  0  important      padding  0  important  margin  0  important      lt  --JavaScript  jQuery  -- gt  jQuery window  load function             chromeHack-autocomplete   delay 100  hide 0  function               this  remove                  I know that it may seem not very elegant but it works

User · Answer

I had a similar issue where the input field took either a name or an email  I set autocomplete  off  but Chrome still forced suggestions  Turns out it was because the placeholder text had the words  name  and  email  in it   For example   lt input type  text  placeholder  name or email  autocomplete  off    gt    I got around it by putting a zero width space into the words in the placeholder  No more Chrome autocomplete    lt input type  text  placeholder  nam amp  8203 e or emai amp  8203 l  autocomplete  off    gt

User · Answer

I call this the sledgehammer approach  but it seems to work for me where all other approaches I tried have failed    lt input autocomplete  off  data-autocomplete-ninja  true  name  fa  id  fa    gt    Note  the input name and id attributes should not contain anything that would give the browser a hint as to what the data is  or this solution will not work  For instance  I m using  fa  instead of  FullAddress    And the following script on page load  this script uses JQuery        data-autocomplete-ninja    each function            this  focus function                this  data  ninja-name     this  attr  name    attr  name               blur function                this  attr  name     this  data  ninja-name                   The above solution should prevent the browser from autofilling data gathered from other forms  or from previous submits on the same form   Basically  I m removing the name attribute while the input is in focus  As long as you re not doing anything requiring the name attribute while the element is in focus  such as using selectors by element name  this solution should be innocuous

User · Answer

Here is what worked for me on Chrome Version 51 0 2704 106  lt input id  user name  type  text  name  user name  autocomplete  off  required   gt   and in combination with  lt input id  user password  type  password  name  user password   autocomplete  new-password  required   gt   My problem was that after implementing new-password it would still show a drop-down of usernames on the user name field

User · Answer

I managed to disable autocomple exploiting this rule   Fields that are not passwords  but should be obscured  such as credit card numbers  may also have a type  quot password quot  attribute  but should contain the relevant autocomplete attribute  such as  quot cc-number quot  or  quot cc-csc quot   https   www chromium org developers design-documents create-amazing-password-forms   lt input id  quot haxed quot  type  quot password quot  autocomplete  quot cc-number quot  gt   However it comes with the great responsibility     Don   t try to fool the browser Password managers  either built into the browser  or external  are designed to ease the user experience  Inserting fake fields  using incorrect autocomplete attributes or taking advantage of the weaknesses of the existing password managers simply leads to frustrated users

User · Answer

TL DR  Tell Chrome that this is a new password input and it won t provide old ones as autocomplete suggestions    lt input type  password  name  password  autocomplete  new-password  gt      autocomplete  off  doesn t work due to a design decision - lots of research shows that users have much longer and harder to hack passwords if they can store them in a browser or password manager   The specification for autocomplete has changed  and now supports various values to make login forms easy to auto complete    lt  -- Auto fills with the username for the site  even though it s email format -- gt   lt input type  email  name  email  autocomplete  username  gt    lt  -- current-password will populate for the matched username input  -- gt   lt input type  password  autocomplete  current-password    gt    If you don t provide these Chrome still tries to guess  and when it does it ignores autocomplete  off    The solution is that autocomplete values also exist for password reset forms    lt label gt Enter your old password       lt input type  password  autocomplete  current-password  name  pass-old    gt   lt  label gt   lt label gt Enter your new password       lt input type  password  autocomplete  new-password  name  pass-new    gt   lt  label gt   lt label gt Please repeat it to be sure       lt input type  password  autocomplete  new-password  name  pass-repeat    gt   lt  label gt    You can use this autocomplete  new-password  flag to tell Chrome not to guess the password  even if it has one stored for this site   Chrome can also manage passwords for sites directly using the credentials API  which is a standard and will probably have universal support eventually

User · Answer

None of the solutions worked except for giving it a fake field to autocomplete   I made a React component to address this issue   import React from  react      Google Chrome stubbornly refuses to respect the autocomplete  off  HTML attribute so    we have to give it a  fake  field for it to autocomplete that never gets  used    const DontBeEvil        gt       lt div style    display   none     gt       lt input type  text  name  username    gt       lt input type  password  name  password    gt     lt  div gt     export default DontBeEvil

User · Answer

2021 answer  Sadly  the only things that work are disgustingly hacky  My solution is to add a dynamically generated random number to the end of the name attribute  E g   lt input name  quot postcode-22643 quot      when generating your front-end markup  This tricks the browser suitably for now  You ll then need to add something server-side to cleanse the incoming post request  For example  within NodeJS   Express  I ve put a middleware in  with a bit of regex to remove the number segment from the received post request  Mine looks like this  but I imagine something pretty similar would be available in other languages  const cleanseAutosuggest   function  req  res  next       for  const key in req body          if  key match  - d                req body key replace  - d     quot  quot      req body key            delete req body key                   next        app post  quot  submit quot   cleanseAutosuggest  function  req  res  next

User · Answer

autocomplete  off  works now  so you can just do the following    lt input id  firstName2  name  firstName2  autocomplete  off  gt    Tested in the current Chrome 70 as well as in all versions starting from Chrome 62   Demo    the top input has the auto complete working the bottom input has the auto complete disabled by adding autocomplete  off

User · Answer

You can use autocomplete  new-password    lt input type  email  name  email  gt   lt input type  password  name  password  autocomplete  new-password  gt    Works in    Chrome  53  54  55 Firefox  48  49  50

User · Answer

Well  a little late to the party  but it seems that there is a bit of misunderstanding about how autocomplete should and shouldn t work  According to the HTML specifications  the user agent  in this case Chrome  can override autocomplete  https   www w3 org TR html5 forms html autofilling-form-controls -the-autocomplete-attribute  A user agent may allow the user to override an element s autofill field name  e g  to change it from  quot off quot  to  quot on quot  to allow values to be remembered and prefilled despite the page author s objections  or to always  quot off quot   never remembering values  However  user agents should not allow users to trivially override the autofill field name from  quot off quot  to  quot on quot  or other values  as there are significant security implications for the user if all values are always remembered  regardless of the site s preferences   So in the case of Chrome  the developers have essentially said  quot we will leave this to the user to decide in their preferences whether they want autocomplete to work or not  If you don t want it  don t enable it in your browser quot   However  it appears that this is a little over-zealous on their part for my liking  but it is the way it is  The specification also discusses the potential security implications of such a move   The  quot off quot  keyword indicates either that the control s input data is particularly sensitive  for example the activation code for a nuclear weapon   or that it is a value that will never be reused  for example a one-time-key for a bank login  and the user will therefore have to explicitly enter the data each time  instead of being able to rely on the UA to prefill the value for him  or that the document provides its own autocomplete mechanism and does not want the user agent to provide autocompletion values   So after experiencing the same frustration as everyone else  I found a solution that works for me  It is similar in vein to the autocomplete  quot false quot  answers  A Mozilla article speaks to exactly this problem  https   developer mozilla org en-US docs Web Security Securing your site Turning off form autocompletion  In some case  the browser will keep suggesting autocompletion values even if the autocomplete attribute is set to off  This unexpected behavior can be quite puzzling for developers  The trick to really force the no-completion is to assign a random string to the attribute  So the following code should work  autocomplete  quot nope quot   And so should each of the following  autocomplete  quot false quot  autocomplete  quot foo quot  autocomplete  quot bar quot   The issue I see is that the browser agent might be smart enough to learn the autocomplete attribute and apply it next time it sees the form  If it does do this  the only way I can see to still get around the problem would be to dynamically change the autocomplete attribute value when the page is generated  One point worth mentioning is that many browser will ignore autocomplete settings for login fields  username and password   As the Mozilla article states   For this reason  many modern browsers do not support autocomplete  quot off quot  for login fields   If a site sets autocomplete  quot off quot  for a form  and the form includes username and password input fields  then the browser will still offer to remember this login  and if the user agrees  the browser will autofill those fields the next time the user visits this page  If a site sets autocomplete  quot off quot  for username and password input fields  then the browser will still offer to remember this login  and if the user agrees  the browser will autofill those fields the next time the user visits this page   This is the behavior in Firefox  since version 38   Google Chrome  since 34   and Internet Explorer  since version 11    Finally a little info on whether the attribute belongs on the form element or the input element  The spec again has the answer   If the autocomplete attribute is omitted  the default value corresponding to the state of the element s form owner s autocomplete attribute is used instead  either  quot on quot  or  quot off quot    If there is no form owner  then the value  quot on quot  is used   So  Putting it on the form should apply to all input fields  Putting it on an individual element should apply to just that element  even if there isn t one on the form   If autocomplete isn t set at all  it defaults to on  Summary To disable autocomplete on the whole form   lt form autocomplete  quot off quot      gt   Or if you dynamically need to do it   lt form autocomplete  quot random-string quot      gt   To disable autocomplete on an individual element  regardless of the form setting being present or not   lt input autocomplete  quot off quot      gt   Or if you dynamically need to do it   lt input autocomplete  quot random-string quot      gt   And remember that certain user agents can override even your hardest fought attempts to disable autocomplete

[html] Chrome ignores autocomplete="off"

Examples related to html

Examples related to google-chrome

Examples related to autocomplete

Examples related to forms