I have run into a somewhat weird problem on a website www.districtconference.org
There is a form on the Registration page that is a pretty standard asp.net based form writing to a database, but what is happening (at least when using Chrome browser), is that first a person registers with their name, address, email etc.
Then they register a guest. As they go along Chrome may offer to auto-fill in, for example, their city. But when they accept an autofill for the city, chrome just might "know" the zip code and state and fill those in too. That's handy.
BUT, Chrome sometimes "knows" too much, and auto-fills in their name too, over-writing the name of their guest that they had already typed in. I have received quite a few registrations where that has happened, and it is easy for the person to miss. Nobody expects to have to go back and make sure a name they entered was not changed because of some auto-filled entry later on in the form.
Anyone else run into this? Not sure what can be done to prevent it ----
Read https://cloudfour.com/thinks/autofill-what-web-devs-should-know-but-dont/ You'll come to the section on the "autocomplete" attribute which you can use.
E.g. to tell the browser you'd like it not to offer to autofill, try
<input name="q" type="text" autocomplete="off"/>
Be aware that browsers don't always follow your instruction when it comes to how it will help respond to a form field.
And in some cases a browser will behave if the form tag has autocomplete = "off", but not when the individual form fields do.
BrightWillow - Asp.Net Applications
Hi, Clark. This isn't a solution for the apparently somewhat variable support for "autocomplete=off," but rather a suggestion to prevent submission of incorrect form data. It would also help the user catch if s/he meant to choose one of the binary choices (bike tour, choir participation, etc.) but didn't.
When the user submits the form, just pop up a window that shows the form data as it will be submitted, with a header, "Please Check Your Registration Information." Without all of the instructions, dropdowns, etc. it will fit within a smaller space that will allow the user to easily scan all the data at once, without having to scroll back up and ignore all the instructions, etc., and can note their option choices, and they should certainly catch it if the name is incorrect (might put that in bold, or a larger face, or both, or...).
If the form data is correct, they click "Continue," and you go ahead and process the form data as entered. If not, they click "Return to Form," whereupon you close that window, leaving them with all their data still there, ready to correct only the field(s) that are incorrect.
Like I said, not a solution for the autocomplete issue across browsers, but it should help you prevent bad data from being submitted.
Please remember to "Mark as Answer" the responses that resolved your issue. It is common courtesy to recognize those who have helped you, and it also makes it easier for visitors to find the resolution later.