Form Autofill in Mozilla creating “invalid inputs”
Hi. A recent user on my website mentioned that she was having problems filling out a form with the same address more than once. Since many of my users have multiple enrollments sent to the same address this is an important issue. So I went myself to the form page and tried to fill out her information and I had the same problem. Certain address line entries showed up with the message (in red) “Please enter a valid input”. Well on the screen was a perfectly valid input, namely, the same input that had been put into the form previously. I noticed that when I returned to the form and entered the first line (my email address) that a number of the slots filled in automatically and were highlighted in a light yellow. Those slots were automatically filled. So I changed one of the slots with a new name that I wanted sent to the same address and when I submitted the form I got the above message. This has never happened before. I have contacted the outfit that supplies my form plugins for support. But I noticed that when I entered the same email address, as I typed there showed up underneath options from previous times I had filled out the form (great!), and under those options the option “Form Autofill Preferences” - so I clicked on that option only to discover that this is a Mozilla feature. So I turned off “Autofill Addresses” and low and behold the plugin works fine. My problem is this: I have many users who use Firefox Mozilla but who are, like the recent user I mentioned, not able to figure out why, all of a sudden, they cannot successfully fill out a form that they have filled out many times before with the same address. This means that frustrated users will simply throw in the towel (and won’t make further transactions). In the next 2 months there will be about about 350 users trying to fill out forms on the website - so this is a critical moment. My question: how can I inform Mozilla that this new Autofill Forms setting is going to be a disaster for many websites and users who utilize registration forms (like summer camps, conventions, etc.)?
[Attached is a screenshot of what is happening]
Todas as respostas (5)
Form Fill is a new feature in Firefox 58; a feature which isn't complete and isn't available to all users yet. Not available in my Firefox installation so I can't even play with it.
File a Bugzilla report, https://bugzilla.mozilla.org/ And read this first to learn how to write an actionable Bug report. https://developer.mozilla.org/en/Bug_writing_guidelines
Make sure to include all details in the bug report.
Please provide public link(s) (no password) that we can check out. No Personal Information Please !
Thanks. I'll report the bug and see what happens.
One update: The "invalid input" with the Firefox autofill ONLY occurs on a form if the address comes after conditional logic. I tried 2 other forms where there was no conditional logic, just a form with an address, and it worked perfectly. I tried 2 other forms with conditional logic and the "invalid input" occurred.
This would be a problem, for example, if a form says "Is the shipping address the same as the billing address?" - if one clicks "no," (conditional logic), then the slots for the billing address would pop-up and this autofill problem would occur.
I reported the bug HERE with all of the steps to replicate the problem - I even created a form just for this purpose so that anyone can give it a try and not be entering "test" entries into somebody else's live form :-)
This may be a problem with the form plugin I'm using (and I'm looking into that); but all I know at this point is that it started and continues with the Firefox autofill feature.
If/when this gets resolved I will post back here.
Looks to be a decent Bug report and that test page appears concise enough to "see" what's related to that form.
<script type='text/javascript' src='http://www.novenamasses.org/wp-includes/js/jquery/jquery.js?ver=1.12.4'></script> <script type='text/javascript' src='http://www.novenamasses.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1'></script> <script type='text/javascript' src='http://www.novenamasses.org/wp-includes/js/jquery/ui/core.min.js?ver=1.11.4'></script> <script type='text/javascript' src='http://www.novenamasses.org/wp-includes/js/jquery/ui/widget.min.js?ver=1.11.4'></script> <script type='text/javascript' src='http://www.novenamasses.org/wp-includes/js/jquery/ui/tabs.min.js?ver=1.11.4'></script> <script type='text/javascript' src='http://www.novenamasses.org/wp-content/themes/kaboodle/kaboodle/functions/js/shortcodes.js?ver=1'></script>
And all those WordPress JavaScript files brings up a question in my mind as to whether that is the latest version of WordPress JS files - 1.11.4 ?? Copyright coded at the bottom of that test page is 2016, which makes me wonder if this is a problem with older JS code??
Look I am not a coder and have no experience with WordPress, but we have had some questions about problems with WordPress as related to "stuff" with WP not working correctly going back a few versions of Firefox, and the answer was the web developer using older WP files which didn't work correctly any longer. https://codex.wordpress.org/WordPress_Versions -- I can't match that up with 1.11.4 so that doesn't seem to be the same versioning system with JS and the main WP version number, but it's something to look into rather than waiting for a response to your Bugzilla report, considering Easter is like 3 weeks away and "time is of the essence" for you.