Autofill populating wrong fields

问题

I have a site with a checkout page that has always worked beautifully.
Recently, any customer that uses autofill to fill out his info, gets his email address dumped into the company field. There are no changes that we did that could affect that. What other tools can I use to get to the bottom of this?

回答1:

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 is being used to guess the "type" of field, and what kind of saved data should be used to populate it.

回答2:

We still don't know what caused the issue, but for anyone seeing this we ended up making the field readonly so that auto-fill doesn't fill it. We then wrote some JS that on focus, it becomes active and the user can manually fill it in.

<input type="text" name="company" readonly="" onfocus="this.removeAttribute('readonly');">

回答3:

Found myself in a similar problem, and the autocomplete property is what to be used in this situations

<input type="text" name="fooBar" autocomplete="organization" > 

exhaustive list of autocomplete/autofill tags for html form inputs

回答4:

I encountered a similar problem, having a "company" field placed under a "name" field. That company field was auto-filled with a birth year. It came from another form on the same site that was displaying a "birthdate" field group just below the "name" field. So chrome stored its auto-fill values in that order. I ended up with changing my second form field order (sadly it was the best I could do).

回答5:

You need to add name to the input tag. Browsers use name to identify what info is supposed to go into the field. You can also use the same for ID and for placeholder if you like. Try this:

<input type="text" name="company" id="company" placeholder="company">

If that still does not work, you might consider turning off autofill for that particular field*:

<input type="text" name="company" id="company" placeholder="company" autocomplete="off">

*you can also turn off autofill for the whole form using the same autocomplete property and off value.

回答6:

The Almost Invisible Input Proxy Trick

I just encountered the same issue with the Chrome 72... It just wanted to fill any kind of field (select or input) as long it was not readonly (with complete no respect for name, autocomplete, etc attributes), with any kind of value it may have stored previously.

• You may want to avoid the field to be populated because you listen on the change event or there are some validation on input that may trigger error message just because of bad autofill.
• You just want the autofill value to be discarded and not even show (even before javascript execution).

You just provide another field for the browser to fill and you make it almost impossible to see by hiding it under the other field.

    <input type="text" id="autofill-if-you-dare" style="position: absolute; z-index: -1; top: 20px; width: 0; height:0" />

Note: You can still hide or remove it by javascript afterwards but you should not hide it before autofilling has been completed, because Chrome will populate only visible fields. And as other answers have stated, it doesn't trigger any event, so you must rely on polling to do so.

回答7:

We recently started having an issue like this with our shopping cart page when it was viewed from chrome and you had a saved user name and password for the site. Chrome would inexplicably put the user name value into the quantity box. After much hair-pulling, we realized that there were a hidden user name and password field on the page. These auto-filled correctly when visible. When hidden chrome would auto-fill the quantity input box. By setting autocomplete="username" and autocomplete="current-password" on these controls the issue went away.

回答8:

I had the problem that chrome will fill in my email in all fields in one of my forms. The other form works correctly. I found the problem is that the word Name must be before the name input. Or the word email must be before input for email. I had it afterwards. Also using <label for="email">Your email</label> after the email input worked.

**Incorrect autocomplete:**
<input type="text" name="name"/> Your name
<input type="email" name="email"/> Your email

**Correct autocomplete:**
Your name <input type="text" name="name"/>
Your email <input type="email" name="email"/>
or
<label for="name">Your name</label> <input type="text" name="name"/>
<label for="email">Your email</label> <input type="email" name="email"/>
or
<input type="text" name="name"/> <label for="name">Your name</label>
<input type="email" name="email"/> <label for="email">Your email</label>

回答9:

I have been encountering this issue lately, specifically with chrome. It seems that

autocomplete="off"

isnt being picked up anymore by Chrome. I found the following sources helpful :

Chromium (which i believe is what a lot of Chrome is based on) has the following code that shows the regex that is used when finding fields to populate with Chrome's autocomplete:

https://cs.chromium.org/chromium/src/components/autofill/core/common/autofill_regex_constants.cc?sq=package:chromium&g=0&l=262

I feel like they only other work around that I have found is to follow these conventions : https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete

Or at least make sure that you give an attribute that's disimilar enough from the above list so it that wont get picked up by autocomplete features.

来源：https://stackoverflow.com/questions/34443628/autofill-populating-wrong-fields