A form should feel easy to use. The visitor sees a question, gives an answer, and needs to know what will happen next.
What You Need to Know
This example uses the browser’s built-in hidden control, so you do not have to create a picker from scratch.
In this example: send a form context identifier.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/add-to-cart" method="post">
<input type="hidden" name="product-id" value="sku-148">
<button type="submit">Add notebook to cart</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.
- <input>: The input is a control. Its type changes the way people enter information.
- type: Type changes what sort of control or resource the browser uses.
What the example shows: The field is not shown on the page but its name and value can be submitted.
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) product-id. 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
Inspect the hidden field in Developer Tools and change its value; observe why a server must not trust it.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Hidden does not mean secret: visitors can view and change this value.
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.