HTML Form Troubleshooting: Value Not Sent to Server

Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.

What You Need to Know

Only controls with names that are successful form controls send values. The disabled request number is omitted.

Try the Example

Take a look at the example. We’ll explain the important lines right below it.

<form action="/support" method="post">
    <label for="request-number">Request number</label>
    <input id="request-number" value="A-108" disabled>
    <label for="request-type">Request type</label>
    <input id="request-type" name="request-type" value="help">
    <button type="submit">Send</button>
</form>

Let’s Read the Code

value: The value is the actual data associated with a control or choice.
<form>: The form groups controls and identifies where submitted data goes.
<label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
for: For connects a label or output with a control by ID.

Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.

What Happens in the Browser?

The HTML controls work in the browser, but saving an answer requires the example action path to be handled by a real server.

Where does the answer go? The example uses the submitted name(s) request-type. Those names help the receiving server identify each answer. A label is for people; a name attribute is for the form data; an ID connects elements in the page.

Your Turn

Open the Network panel, submit the form, and compare what arrives before and after adding disabled. Which values disappear?

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
Inspect name and disabled before looking for a server bug.

Key Takeaways

A control needs a clear label and, when submitted, a meaningful name and value.
value: The value is the actual data associated with a control or choice.
Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.