Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
Here is a small, realistic example focusing on formnovalidate and novalidate.
In this example: create a Save Draft button that bypasses validation.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/submit" method="post">
<label for="student-email">Email</label>
<input id="student-email" type="email" name="email" required>
<button type="submit">Submit with browser checks</button>
<button type="submit" formnovalidate>Submit without browser checks</button>
</form>Let’s Read the Code
- <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.
- id: An id uniquely identifies an element on this page.
What the example shows: The markup gives the browser a clear starting point for formnovalidate and novalidate. Look at the labels, names, and values rather than only the visual appearance.
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.
How can you test it? Submit once with an empty field, once with a clearly invalid value, and once with a valid value. Watch which rule blocks submission. These are helpful browser checks; your server must validate all received data again.
Your Turn
Change one meaningful attribute, submit the form, and compare the result with the original.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- These browser-side hints improve the experience, but the server must still validate submitted information.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- <form>: The form groups controls and identifies where submitted data goes.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.