A webpage is not always broken because of a large mistake. Small details can produce exactly this problem: debugging: space and newline rendering confusion. This guide shows you what to look for, a concrete fix, and how to check that it worked.
The Idea in Plain English
HTML normally collapses sequences of whitespace in text, so newlines in source are not necessarily visible line breaks.
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
The first part shows a problem. The second part shows a safer or more accurate version. Compare them before reading the explanation.
<!-- Problem -->
<p>One two
three</p>
<!-- Corrected example -->
<p>One two<br>three</p>
<pre>One two
three</pre>What Each Part Does
- A paragraph keeps one idea together as readable text.
- The br element inserts a line break within text.
- The pre element preserves text spacing and line breaks.
Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
Try It Yourself
Compare paragraph text with preformatted output in the browser.
Common Beginner Mistakes
- Check the underlying cause before changing unrelated tags.
- 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
- HTML normally collapses sequences of whitespace in text, so newlines in source are not necessarily visible line breaks.
- Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.