A small piece of HTML can change what a visitor sees or how the browser understands a page. In this lesson, you will explore nested forms: invalid markup and browser recovery using a short example that you can inspect and change.
The Idea in Plain English
A form-associated control usually belongs to its nearest ancestor form. An explicit form attribute can associate certain controls with a form elsewhere in the same document, using a form ID.
You can test this using a small local HTML file. Change one part at a time and check the result in the browser before adding more code.
A Working Example
Read the sample once before copying it. Notice the element names and attribute values, then compare them with the explanation below.
<form id="registration" action="/register" method="post">
<label for="display-name">Display name</label>
<input id="display-name" name="display_name" required>
</form>
<button type="submit" form="registration">Join</button>What Each Part Does
- The form collects and submits named fields to the destination specified by action.
- The label tells visitors and assistive tools what a control is for.
- The input creates a field; its type changes the editing controls and the name identifies submitted data.
- id names an element for labels, fragments, CSS or JavaScript; IDs should be unique.
- for connects a visible label to the control with the same ID.
- action sets the URL that receives a submitted form.
A button outside the visual form can still submit it when form="registration" matches the form id.
Keep the example small while learning. Once it behaves as expected, try it inside a larger page and make sure the URLs, files and surrounding HTML are correct.
Try It Yourself
Try this next: compare authored source against the DOM tree in DevTools focused on Nested Forms: Invalid Markup and Browser Recovery, including a working example and an incorrect example to correct. Then inspect the page and explain what changed.
Common Beginner Mistakes
- Nesting forms inside forms or expecting controls with no name to be sent.
- Changing several parts of the example at once, making it difficult to see which part caused a different result.
- Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.
Key Takeaways
- A form-associated control usually belongs to its nearest ancestor form. An explicit form attribute can associate certain controls with a form elsewhere in the same document, using a form ID.
- A button outside the visual form can still submit it when form="registration" matches the form id.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.