Inconsistent formatting of source code

[Alfonso Martínez de Lizarrondo]

1. Load the Ajax example in Firefox.
2. Switch to source mode. it shows

   <p>
   	<br />
   </p>
   

3. Switch to design and back to source. The formatting has changed

   <p>
   	<br />
   	</p>
   

(the closing </p> now is indented)

[Garry Yao]

The current parser already has a way of removing head spaces,now the proposed patch make the parser awareness of the tail spaces by pending each text node, both of them could guarantee that the writer won't confuse these formatting spaces with user spaces, to correctly indent the output of a element, one example: If input as:

<p>
<br />
	<p>

Basic writer normalize it into:

<p><br /><p>

Html writer format it as :

<p>
	<br />
</p>

[Garry Yao]

Fixing a bug when there's a single text node within body.

[Frederico Caldeira Knabben]

We could try a simpler approach here. When closing a tag, we could simply check if its an block(like) tag, and them check if the last child of it is a text node. In that case, we simply rtrim it, and eventually remove it if it becomes empty after trimming.

This check is supposed to happen after line 249 on fragment.js (at revision 3564).

[Garry Yao]

The new patch used an simplified way to right trim the block tail spaces, the check is happened inside addElement function to make sure it works even for the wrapper paragraph introduced by fix body.

[Garry Yao]

Fixed with [3606].