The best answers to the question “HTML 5: Is it <br>, <br/>, or <br />?” in the category Dev.
I’ve tried checking other answers, but I’m still confused — especially after seeing W3schools HTML 5 reference.
I thought HTML 4.01 was supposed to “allow” single-tags to just be
<br>. Then XHTML came along with
<img /> and
<br /> (where someone said that the space is there for older browsers).
Now I’m wondering how I’m supposed to format my code when practicing HTML 5.
I think this quote from the HTML 5 Reference Draft provides the answer:
184.108.40.206 Void Elements
The term void elements is used to designate elements that must be empty. These requirements only apply to the HTML syntax. In XHTML, all such elements are treated as normal elements, but must be marked up as empty elements.
These elements are forbidden from containing any content at all. In HTML, these elements have a start tag only. The self-closing tag syntax may be used. The end tag must be omitted because the element is automatically closed by the parser.
A void element in the HTML syntax. This is not permitted in the XHTML syntax.
A void element using the HTML- and XHTML-compatible self-closing tag syntax.
A void element using the XHTML-only syntax with an explicit end tag. This is not permitted for void elements in the HTML syntax.
In other words:
- Invalid HTML:
- Valid HTML:
And while HTML forbids certain closing tags, xhtml requires them:
- Invalid xhtml:
- Valid xhtml:
Other elements that are forbidden from having a closing tag in HTML:
|Element||Valid HTML||Valid xhtml|
The fact that HTML forbids certain closing tags, while xhtml requires them is xhtml’s problem. If you’re writing HTML, you follow the HTML rules.
At the same time, browers gave up trying to enforce the standards, because everyone gets it wrong. It’s not obvious:
And then xhtml came along, with it’s XML rule that every element must have a closing tag, and people just assumed that HTML was the same thing. So the standards gave up, and were later revised to throw up their hands to the reality.
<BR> is the only true form.
<br> is sufficient.
The other forms are there for compatibility with XHTML; to make it possible to write the same code as XHTML, and have it also work as HTML. Some systems that generate HTML may be based on XML generators, and thus do not have the ability to output just a bare
<br> tag; if you’re using such a system, it’s fine to use
<br/>, it’s just not necessary if you don’t need to do it.
Very few people actually use XHTML, however. You need to serve your content as
application/xhtml+xml for it to be interpreted as XHTML, and that will not work in old versions of IE – it will also mean that any small error you make will prevent your page from being displayed in browsers that do support XHTML. So, most of what looks like XHTML on the web is actually being served, and interpreted, as HTML. See Serving XHTML as text/html Considered Harmful for some more information.
In HTML (up to HTML 4): use
In HTML 5:
<br> is preferred, but
<br /> is also acceptable
<br /> is preferred. Can also use
<br></br>is not valid in HTML 5, it will be thought of as two line breaks.
- XHTML is case sensitive, HTML is not case sensitive.
- For backward compatibility, some old browsers would parse XHTML as HTML and fail on
XML doesn’t allow leaving tags open, so it makes
<br> a bit worse than the other two. The other two are roughly equivalent with the second (
<br/>) preferred for compatibility with older browsers. Actually, space before
/ is preferred for compatibility sake, but I think it only makes sense for tags that have attributes. So I’d say either
<br />, whichever pleases your aesthetics.
To sum it up: all three are valid with the first one (
<br>) being a bit less “portable”.
Edit: Now that we’re all crazy about specs, I think it worth pointing out that according to dev.w3.org:
Start tags consist of the following
parts, in exactly the following order:
- A “<” character.
- The element’s tag name.
- Optionally, one or more attributes, each of which must be
preceded by one or more space
- Optionally, one or more space characters.
- Optionally, a “https://stackoverflow.com/” character, which may be present only if the
element is a void element.
- A “>” character.