TinyMCE inserts blank lines after paragraph with image with caption

[gerobe]

TinyMCE inserts blank lines with a nobreaking space entity after paragraph with image with caption.

This happens, when the text starts right after the last caption

Example:

[caption id="attachment_6120" align="alignleft" width="220" caption="Caption under image"]<img class="size-medium wp-image-6120" title="title" src="http://www.domain.com/wp-content/images/image.jpg" alt="alt text" width="220" height="165" />[/caption]First paragraph with some text.

Second paragraph with some text.

becomes

[caption id="attachment_6120" align="alignleft" width="220" caption="Caption under image"]<img class="size-medium wp-image-6120" title="title" src="http://www.domain.com/wp-content/images/image.jpg" alt="alt text" width="220" height="165" />[/caption]

First paragraph with some text.

&nbsp;

Second paragraph with some text.

after switching to visuell and back to HTML in the editor.

I can't reproduce this.

No matter how I try to put in a post (either starting with visual or html, and bouncing back and forth, saving in between), I never get extra  

Probably a browser specific issue with TinyMCE.

This happens on Win7 with Firefox 3.6.13 and Safari

There are a number of "lost formatting" issues with TinyMCE that occur if you switch back and forth between the Visual and HTML tabs.

I was checking tiny_mce_src.js from its nightly build, saw some todo( commented out code ).

// Use BR instead of &nbsp; padded P elements inside editor and use <p>&nbsp;</p> outside editor
/*
if (o.set)
	h = h.replace(/<p>\s+(&nbsp;|&#160;|\u00a0|<br \/>)\s+<\/p>/g, '<p><br /></p>');
else
	h = h.replace(/<p>\s+(&nbsp;|&#160;|\u00a0|<br \/>)\s+<\/p>/g, '<p>$1</p>');
*/

// Since Gecko and Safari keeps whitespace in the DOM we need to
// remove it inorder to match other browsers. But I think Gecko and Safari is right.
// This process is only done when getting contents out from the editor.

I guess it is the expected behavior.

quick fix

Attached a quick fix, just in case. I'm not much familiar with tiny mce so not touching it.

Since this is expected behavior (with minimal ramifications, and likely some unknown benefit), we should stick with the TinyMCE implementation.