the_content spits out bogus BR tag

[kickslop]

When calling the_content() via, say... archives.php, a BR tag is spit out even if the page is empty.

Let me try explaining that in more detail.

Calling the_content() from a page template PHP file (like archives.php in some themes) should drag in the contents of the actual page itself, as written by the page author. When the Wordpress page content is BLANK (read: "just spit out only what the page template generates"), the_content() is still generating a BR tag.

It causes bogus whitespace that is not wanted.

Not really a bug, so gonna switch this to an enhancement.

a separate patch is needed for the js version of wpautop in wp-admin/js/editor.js. you can see tinymce add the <br /> back and forth as you switch to and from the wysiwyg.

but as the code is minified, it's not easy to read or edit.

Replying to Denis-de-Bernardy:

but as the code is minified, it's not easy to read or edit.

See editor.dev.js

Replying to Denis-de-Bernardy:

you can see tinymce add the <br /> back and forth as you switch to and from the wysiwyg.

How? I cannot get mine to do that.

Replying to jbsil:

Replying to Denis-de-Bernardy:

you can see tinymce add the <br /> back and forth as you switch to and from the wysiwyg.

How? I cannot get mine to do that.

In Camino, you actually see the transformed code for a fraction of a second before things switch to Wysiwyg view.

TinyMCE uses <br /> to pad the empty editor so the cursor can be placed in it. That's removed during the save cleanup. Think the <br /> in an empty post comes from autop (next line after the proposed fix in the first patch).

(In [11048]) Don't output <br /> for empty posts, props Denis-de-Bernardy, fixes #6128

we're not fixing the js too?

Replying to Denis-de-Bernardy:

we're not fixing the js too?

It doesn't happen there, see the previous comment.

oh, sorry, I had missed your comment.