Can't Prevent Google Chrome From Auto filling Field
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
This question has been asked before and I'm asking again because none of the answers worked.
I've got a form on my checkout page where I have autocomplete="off"
in the <form>
tag.
My form contains address information. Specifically, I have a field named address_line_two
which should not be auto filled. So, on this input I set autocomplete="false"
on this input field. This works on my PC, but I have video monitoring installed on my site and several of my chrome users are able to auto fill the address_line_two
field. I also see the duplicated auto fill data in my database as a result. I am referring to the Google auto fill function that automatically populates a form with a previously saved address. Is there an updated work around to this issue?
jquery html css google-chrome
add a comment |
This question has been asked before and I'm asking again because none of the answers worked.
I've got a form on my checkout page where I have autocomplete="off"
in the <form>
tag.
My form contains address information. Specifically, I have a field named address_line_two
which should not be auto filled. So, on this input I set autocomplete="false"
on this input field. This works on my PC, but I have video monitoring installed on my site and several of my chrome users are able to auto fill the address_line_two
field. I also see the duplicated auto fill data in my database as a result. I am referring to the Google auto fill function that automatically populates a form with a previously saved address. Is there an updated work around to this issue?
jquery html css google-chrome
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14
add a comment |
This question has been asked before and I'm asking again because none of the answers worked.
I've got a form on my checkout page where I have autocomplete="off"
in the <form>
tag.
My form contains address information. Specifically, I have a field named address_line_two
which should not be auto filled. So, on this input I set autocomplete="false"
on this input field. This works on my PC, but I have video monitoring installed on my site and several of my chrome users are able to auto fill the address_line_two
field. I also see the duplicated auto fill data in my database as a result. I am referring to the Google auto fill function that automatically populates a form with a previously saved address. Is there an updated work around to this issue?
jquery html css google-chrome
This question has been asked before and I'm asking again because none of the answers worked.
I've got a form on my checkout page where I have autocomplete="off"
in the <form>
tag.
My form contains address information. Specifically, I have a field named address_line_two
which should not be auto filled. So, on this input I set autocomplete="false"
on this input field. This works on my PC, but I have video monitoring installed on my site and several of my chrome users are able to auto fill the address_line_two
field. I also see the duplicated auto fill data in my database as a result. I am referring to the Google auto fill function that automatically populates a form with a previously saved address. Is there an updated work around to this issue?
jquery html css google-chrome
jquery html css google-chrome
asked Feb 7 '18 at 22:34
Cannon MoyerCannon Moyer
1,1381919
1,1381919
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14
add a comment |
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14
add a comment |
1 Answer
1
active
oldest
votes
The browser is going to remember the values provided to the autocomplete attribute for future use. So for individual users that have filled out different forms made by developers with different naming conventions, the fields will populate accordingly.
Most users like autofill and want it to run. You could give your input a random auto-complete value to prevent auto-complete from running, but, it will likely slow users down.
<input autocomplete="address-line2">
The attribute above above follows chrome's recommended settings for forms, so most liekly to grab the right string to cram into the input. That will probably net you the most correctly auto filled forms over time.
If you take this advice make sure to do the same naming convention for address line 1:
<input autocomplete="address-line1">
Please note I left out a all of other attributes and values you need for an input field to simplify the answer.
Here is some documentation I drew from.
https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill
This quote is from the documentation link:
"For one address input: street-address For two address inputs: address-line1 , address-line2 address-level1 (state or province) address-level2 (city) postal-code (zip code) country"
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48674433%2fcant-prevent-google-chrome-from-auto-filling-field%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The browser is going to remember the values provided to the autocomplete attribute for future use. So for individual users that have filled out different forms made by developers with different naming conventions, the fields will populate accordingly.
Most users like autofill and want it to run. You could give your input a random auto-complete value to prevent auto-complete from running, but, it will likely slow users down.
<input autocomplete="address-line2">
The attribute above above follows chrome's recommended settings for forms, so most liekly to grab the right string to cram into the input. That will probably net you the most correctly auto filled forms over time.
If you take this advice make sure to do the same naming convention for address line 1:
<input autocomplete="address-line1">
Please note I left out a all of other attributes and values you need for an input field to simplify the answer.
Here is some documentation I drew from.
https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill
This quote is from the documentation link:
"For one address input: street-address For two address inputs: address-line1 , address-line2 address-level1 (state or province) address-level2 (city) postal-code (zip code) country"
add a comment |
The browser is going to remember the values provided to the autocomplete attribute for future use. So for individual users that have filled out different forms made by developers with different naming conventions, the fields will populate accordingly.
Most users like autofill and want it to run. You could give your input a random auto-complete value to prevent auto-complete from running, but, it will likely slow users down.
<input autocomplete="address-line2">
The attribute above above follows chrome's recommended settings for forms, so most liekly to grab the right string to cram into the input. That will probably net you the most correctly auto filled forms over time.
If you take this advice make sure to do the same naming convention for address line 1:
<input autocomplete="address-line1">
Please note I left out a all of other attributes and values you need for an input field to simplify the answer.
Here is some documentation I drew from.
https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill
This quote is from the documentation link:
"For one address input: street-address For two address inputs: address-line1 , address-line2 address-level1 (state or province) address-level2 (city) postal-code (zip code) country"
add a comment |
The browser is going to remember the values provided to the autocomplete attribute for future use. So for individual users that have filled out different forms made by developers with different naming conventions, the fields will populate accordingly.
Most users like autofill and want it to run. You could give your input a random auto-complete value to prevent auto-complete from running, but, it will likely slow users down.
<input autocomplete="address-line2">
The attribute above above follows chrome's recommended settings for forms, so most liekly to grab the right string to cram into the input. That will probably net you the most correctly auto filled forms over time.
If you take this advice make sure to do the same naming convention for address line 1:
<input autocomplete="address-line1">
Please note I left out a all of other attributes and values you need for an input field to simplify the answer.
Here is some documentation I drew from.
https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill
This quote is from the documentation link:
"For one address input: street-address For two address inputs: address-line1 , address-line2 address-level1 (state or province) address-level2 (city) postal-code (zip code) country"
The browser is going to remember the values provided to the autocomplete attribute for future use. So for individual users that have filled out different forms made by developers with different naming conventions, the fields will populate accordingly.
Most users like autofill and want it to run. You could give your input a random auto-complete value to prevent auto-complete from running, but, it will likely slow users down.
<input autocomplete="address-line2">
The attribute above above follows chrome's recommended settings for forms, so most liekly to grab the right string to cram into the input. That will probably net you the most correctly auto filled forms over time.
If you take this advice make sure to do the same naming convention for address line 1:
<input autocomplete="address-line1">
Please note I left out a all of other attributes and values you need for an input field to simplify the answer.
Here is some documentation I drew from.
https://developers.google.com/web/updates/2015/06/checkout-faster-with-autofill
This quote is from the documentation link:
"For one address input: street-address For two address inputs: address-line1 , address-line2 address-level1 (state or province) address-level2 (city) postal-code (zip code) country"
edited Jan 4 at 16:48
answered Feb 7 '18 at 23:07
JakeJake
14
14
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48674433%2fcant-prevent-google-chrome-from-auto-filling-field%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is so important about not autofilling this specific field?
– Kevin B
Feb 7 '18 at 23:10
Chrome autofills address_line_one correctly, but then autofills address_line_two with the same information as address_line_one. When you save an address in chrome, there isn't an address_line_two option anyway. If there is a technically correct approach I'm all about it but haven't seen one yet. @KevinB
– Cannon Moyer
Feb 7 '18 at 23:14