HTML Formnovalidate for Draft-Saving Buttons

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

What You Need to Know

Here is a small, realistic example focusing on formnovalidate for draft.

Try the Example

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

<form action="/save" method="post">
    <label for="story-title">Story title</label>
    <input id="story-title" name="story-title" required>
    <button type="submit">Publish</button>
    <button type="submit" formnovalidate name="action" value="draft">Save draft</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 for draft. 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.

Look at the submitted value. The picker may display a friendly calendar or local clock, while form values use specific machine-readable formats. A local date and time does not automatically carry a time-zone identifier. Compare what you see with what your application receives.

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.
A browser may render the control differently from another browser without changing the HTML meaning.

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.