Extra Space between Page Breaks after moving from Source to Wysiwyg mode.

[naresh.sivaraman]

Tested in IE8.

To reproduce: (1)Add two page breaks on the editor. (2)Remove the line(gap) between them. (3)Go to source and come back to wysiwyg. (4)The line and the gap is back.

Issue is happening because on doing step 2, the div of the second page break falls inside the <p>. This can be seen when we move to source. So, when we come back to wysiwyg, the <p> is closed with a &nbsp;</p> and the div is seperate.

[garry.yao]

We've been suffering from the problem that the fake elements (image) that we use were treated by the browser as they were, even it's been displayed as block.

After 3.4, we introduced the contenteditable support, a nice substitution of fake elements in certain cases, the advantages include:

1. True semantic (no more '_cke_real_element_type' );
2. Better performance on output(no fake element transformation);

The patch propose an attempt in this approach.

[garry.yao]

The bug affects also FF.

[Saare]

Patch should be updated.

[Saare]

• Add a page break. Click it.
• See that the format combo displays div. Open the combo and click on div.

Note that a bookmark is being added above.

[garry.yao]

Ok, I've made a change to styles plugin which disallows style change on read-only blocks.

[Saare]

The object now becomes unselectable thus it cannot be dragged (IE at least). This is counterintuitive. Note that this attribute should not be outputed, in any case.

[Saare]

• Create the following selection:

  <p>
  	text [text text</p>
  <div style="page-break-after: always;" title="Page Break">
  	<span style="display: none;">&nbsp;</span></div>
  <p>
  	text text] text</p>
  

• In the format combo, choose "heading 2".

Result: div is transformed into h2.
Also, on output, the page break should not have the title attribute.

[garry.yao]

The style application issue is a current editor limitation, filed #7694.

[garry.yao]

Fixed with [6764], thanks Saar for the high quality review.