Open the console first
“Not submitting” has a precise meaning worth checking before anything else: open DevTools, watch the Network tab, click Send. If a request appears, your form submits and the problem lives server-side or in the response handling, which is a different guide. If no request appears, one of these five is the cause:
| The switch | What you observe |
|---|---|
| Button with type="button", or outside the form | Click does nothing, console silent |
| Hidden required field | Console: “invalid form control … is not focusable” |
| A field named submit | Scripts throw “form.submit is not a function” |
| Disabled submit button | Button greyed out or styled normal but inert |
| preventDefault() and then a silent failure | Handler runs, no request, maybe a thrown error |
A field named submit
Every form element becomes a property on the form object under its name, and a field named submit replaces the form's submit() method with itself. Any script that then calls form.submit(), including plenty of third-party ones, throws. Our test page threw TypeError: document.getElementById(...).submit is not a function on the first call.
Clicking the button may still work in this case, which makes the breakage look random: hand-clicks submit, scripted submits crash. Rename the field (submit-button, or any name that is not a form property, and the same goes for a field named action or method), and the method comes back. Contact Form 7's FAQ keeps a whole list of names WordPress additionally reserves, which is why its default fields are prefixed your-.
Disabled buttons and handlers that eat the event
A disabled submit button is inert by definition, and the subtle version is a script that disables the button to prevent double-clicks and fails to re-enable it after a validation error, so the second attempt is impossible. If clicking produces no focus outline and no console line, inspect the button element and look for the attribute.
The JavaScript variant of “nothing happens” is a submit handler that calls event.preventDefault() and then never completes its own sending: a typo before the fetch, a failed import, a condition that returns early. The form's default behaviour is switched off, the replacement never runs, and the visitor sees nothing at all. The console usually shows the thrown error; if the handler fails silently, add a temporary console.log at its first line to confirm it runs at all. And after any of these fixes, test logged out and past your page cache: a cached page can keep serving the broken script long after you fixed it.
A form that has less to break
Three of the five switches live in custom JavaScript or in markup drift. A plain HTML form posting to a backend needs neither: no handler, no fetch, no re-enable logic, just action, method="POST" and named fields. With Formgong the endpoint also stores every submission in a dashboard inbox and delivers to email and Telegram, and the HTML guide is a one-page setup; our form checker will tell you whether an existing form actually sends anything. The free plan takes 1,000 submissions a month.
Which switch was it?
Did one of the five match your form, or did the Network tab show something this page does not cover? Write to support@formgong.com and tell us what you tried. The cases readers send are how these guides get better.
Frequently asked questions
Why does my HTML form do nothing when I click submit?
Check five things: the button's type attribute (type="button" never submits), a hidden field with required (the console shows “is not focusable”), a field named submit (breaks form.submit()), a disabled button, and a JavaScript handler that calls preventDefault() and then fails. The browser console identifies most of them.
What does “An invalid form control is not focusable” mean?
A required field failed validation, but it is hidden (display:none), so the browser cannot focus it to show the message and aborts the submission instead. Remove required from hidden fields, disable them while hidden, or validate with your own code under novalidate.
Why does form.submit() throw “is not a function”?
The form has a field named submit, which shadows the method: form elements become properties of the form under their names. Rename the field and the method works again.
How do I tell whether the form submits at all?
Open DevTools, switch to the Network tab and click the button. A request appearing means the form submits and the problem is the server or the response handling; no request means the submission is blocked on the page, by one of the five switches above.
Sources and documentation
Official references for this guide: MDN: button type attribute, MDN: HTMLFormElement.submit(), MDN: Constraint validation. HTML contact form, where data is stored.