As people have pointed out: Adding "</br>" to a list of approved tags doesn't really make sense ... since it's not a tag, it's a missued closing tag. if you don't open a br, you can't close it.. and the site currently (and correctly) strips out uneeded closing tags -- warning you about them if you are viewing at the necessary HTML error reporting level

This smells like an X/Y problem discussion...

If the concern is "unsightly </br> instances showing up in posts", then perhaps the problem is not doing something auto-magically to fix them and guess what the author intended, but instead get the author to do what they ment to do correctly. Perhaps the questions to ask are:

• Do we really need an "HTML error reporting during Preview" setting? Why not force people to preview at the highest possible error reporting level?
• Why do we let people post content with malformed (ie: invalid or unclosed) tags? If the preview screen detects and reports on html errors, why not just report those errors in bright RED instead of light grey) and suppress the "create" button so they have to fix the errors and hit preview again?

Sure, people might *add* errors after previewing a valid post, or while updating an existing doc ... i'm not suggesting we give a 404 if they do click submit after entering malformed HTML ... but why not discourage it as much as (easily) possible?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.