A small piece of HTML can change what a visitor sees or how the browser understands a page. In this lesson, you will explore implied end tags and unexpected parentage using a short example that you can inspect and change.
The Idea in Plain English
Some HTML end tags are optional only under specific grammar conditions. Omitting them can be valid, but explicit closing tags are easier to read and teach beginners.
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.
<ul>
<li>Apples</li>
<li>Oranges</li>
</ul>What Each Part Does
- A ul is an unordered list of related items.
- An li is a single list item.
The browser constructs equivalent DOM nodes where omission is allowed.
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 Implied End Tags and Unexpected Parentage, including a working example and an incorrect example to correct. Then inspect the page and explain what changed.
Common Beginner Mistakes
- Omitting an end tag everywhere because one element, such as li, permits it in certain positions.
- 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
- Some HTML end tags are optional only under specific grammar conditions. Omitting them can be valid, but explicit closing tags are easier to read and teach beginners.
- The browser constructs equivalent DOM nodes where omission is allowed.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.