Firefox letting a form submit with an empty required field is usually a page-level problem, not a broken browser. The page may be switching validation off, or your Firefox preference for it may be turned off.
Inspect the form for novalidate or formnovalidate, set forms.formvalidation.enable to true in the Config Editor, then reload the page and test with a value that breaks the rules.
In this guide, I have covered:
Contents
Why Firefox Skips Its Built-In Form Checks
You press Submit on an empty required field, expecting the browser to stop you, and the page sails on to the next screen instead. Firefox is supposed to block that submit and point at the field. When it doesn’t, one of two things is happening.
Native form validation is Firefox’s built-in check for required fields, input types, and other HTML constraints. The browser runs it before anything reaches the server. If the feature is switched off in your settings, or the page is overriding it, that check never runs.
Start with the page’s HTML. A form carrying novalidate, or a submit button carrying formnovalidate, is telling Firefox to skip interactive validation. JavaScript can also change a field’s validity or submit the form without going through the normal checks.
Mozilla’s support thread on this symptom is at Problems with form validation in Firefox.
TIP: Before you change any Firefox setting, open the same form in another browser. If it fails there too, the page is the culprit, not your profile.
Check Whether the Form Disables Validation
Before you touch Firefox preferences, look at the page itself. The cause is often sitting in plain sight in the markup, and five minutes of inspection saves a lot of guessing.
- Right-click the form and select Inspect to open Firefox’s developer tools.
- Find the <form> element and check whether it contains a novalidate attribute.
- Find the button or input that submits the form and check whether it contains a formnovalidate attribute.
- Remove either attribute from the page’s code, or ask the site’s developer to remove it, and reload the page.
If you don’t control the page code, rebuild the same form in a page you do control, or ask the site owner to correct it. You’ll know it worked when the form refuses an empty required field after a reload.
Enable Native Form Validation in Firefox
If the markup looks clean, the next stop is Firefox’s own preference for this feature. The setting you need is forms.formvalidation.enable.
- Open the
menu and select Settings. - Scroll to the bottom of the General panel.
- Select .
- Accept the warning about making advanced changes.
- Search for forms.formvalidation.enable.
- Set the preference to true, or select Toggle if it is showing false.
- Reload the affected page and submit the form again.
Validation should appear as soon as a field breaks the form’s rules. If the preference doesn’t exist in your build, don’t guess at a similar name. Go back to the page-level checks instead.
The preference name is case-sensitive. Searching a different spelling, or flipping an unrelated setting, only makes the next round of troubleshooting harder.
Check for JavaScript That Skips Validation
A form can look correct in the source and still behave differently once its scripts run. Pay particular attention to code that submits the form directly or rewrites a field’s validity state.
- Open the developer tools with Inspect and switch to the Console panel.
- Reload the page and watch for messages about form submission, validation, or custom validity.
- Search the page’s JavaScript for calls that submit the form without using its normal submit button.
- Remove code that submits the form directly unless it runs an equivalent validation check first.
Also look for code that sets a custom validation message. If a field is left with a custom error, the form stays invalid even when the value you typed looks perfectly fine.
You’ll know the script was the problem when the form validates normally with the direct submit call removed.
Test the Form Correctly
Clicking Submit with every field empty tells you less than you’d think. Use the page’s normal submit button and type a value you know breaks the rules. An empty required field is the clearest test, and an invalid email address or a number outside a declared range confirms it just as well.
- Reload the page after changing the preference or the page code.
- Type an invalid value into a field that uses a constraint such as required, email, minlength, or maxlength.
- Select the form’s normal submit button.
- Confirm that Firefox displays a validation message and does not submit the form.
A blank, untouched email field proves nothing: length and type constraints are checked against what you actually typed, so enter something first. The same logic applies to any constraint that depends on user input.
Check for Extensions and Site Interference
Still no message? Something in your Firefox setup may be altering the page before you ever see it.
If validation still does not appear, a content-changing extension or a broken page script is the likely suspect. Firefox’s browser settings reset guide explains how to reset Firefox without removing your profile data, but troubleshoot extensions first.
- Open the
menu and select Add-ons and Themes. - Review extensions that modify forms, webpages, developer tools, or scripts.
- Disable the relevant extensions temporarily and reload the form.
- Test the form again before changing any other settings.
TIP: A private window is faster than disabling extensions one at a time. An extension only runs there if you have explicitly allowed it.
If the form works with extensions disabled, update or remove the one that caused the conflict. If it still fails, the problem is more likely in the page markup, its JavaScript, or the site’s validation design.
What to Do If the Form Still Submits
If Firefox still lets the form through with no message, you need to know whether the fault is browser-wide or specific to one site. A throwaway test form answers that in a couple of minutes.
- Open a new tab and build a simple form with a required text input and a normal submit button.
- Submit the form without entering a value.
- Check whether Firefox blocks the submission and shows a validation message.
- If the simple form works, report the problem to the website owner and include the page’s form markup details.
If the simple form submits too, go back to forms.formvalidation.enable and check whether another extension or a profile-level setting is interfering.
Frequently Asked Questions
These are the questions that come up most often once the checks above are done.
How do I turn native form validation back on in Firefox?
Open Firefox’s Config Editor, search for forms.formvalidation.enable, and set it to true. Reload the affected page afterward.
Does the novalidate attribute disable Firefox form validation?
Yes. A novalidate attribute on the form, or a formnovalidate attribute on its submit control, tells the browser not to perform interactive validation.
Why does JavaScript prevent Firefox from showing a validation message?
JavaScript can submit a form directly or change a field’s validity state. Direct submission skips the normal interactive check, while an unresolved custom validity message can leave the form invalid.
Why is Firefox not validating a required field?
Check whether the form or submit control disables validation, and inspect the page for JavaScript that changes the field’s validity. Then reload the page, because changes to Firefox’s configuration don’t reach a page that is already open.
If the field still passes with no message and no markup reason, the page is overriding the browser. At that point the fix belongs to the site owner, not to your settings.
