Opened 3 years ago

Last modified 3 years ago

#13840 confirmed Bug

Automatic Paragraph Closing Creates Empty Paragraph

Reported by: Aron Pasieka Owned by:
Priority: Normal Milestone:
Component: General Version: 3.0
Keywords: Cc: ckeditor@…

Description

Steps to reproduce

  1. In Source mode, create a paragraph tag that contains a div, e.g.
    <p>Lorem<div>ipsum</div>dolor...</p>
    <p>... sit amet...</p> 
    
  2. Toggle back to WYSIWYG mode.

Expected result

Paragraph tags have been closed and (in the above example) we are left with 4 block tags.

<p>Lorem<p>
<div>ipsum</div>
<p>dolor...</p>
<p>... sit amet...</p>

Actual result

An empty paragraph has been added after the repaired paragraph.

<p>Lorem<p>
<p>ipsum</p>
<p>dolor...</p>
<p>&nbsp;</p>
<p>... sit amet...</p>

(And the div has been replaced by a p, but that's a separate concern.)

Other details (browser, OS, CKEditor version, installed plugins)

Reproduced in Chrome 46.0.2490.71 m and Firefox 41.0.1 on Windows 7.

Change History (4)

comment:1 Changed 3 years ago by Will Spaetzel

Cc: ckeditor@… added

comment:2 Changed 3 years ago by Aron Pasieka

Typo in Expected and Actual results:

<p>Lorem<p>

should say

<p>Lorem</p>

comment:3 Changed 3 years ago by Jakub Ś

Status: newconfirmed
Version: 4.5.43.0

(And the div has been replaced by a p, but that's a separate concern.)

This is because you are using standard package or other one which doesn't have div plugins included. The DIV is converted to P by ACF. This part of ticket is invalid as editor works as expected here.


An empty paragraph has been added after the repaired paragraph.

This part is valid and can be reproduced from CKEditor 3.0 in all browsers.

comment:4 Changed 3 years ago by Aron Pasieka

(And the div has been replaced by a p, but that's a separate concern.)

This is because you are using standard package or other one which doesn't have div plugins included. The DIV is converted to P by ACF. This part of ticket is invalid as editor works as expected here.

Thanks for that. It wasn't something I was experiencing in our implementation, just on the demo page so I wasn't overly worried about it. Your explanation makes sense.

Note: See TracTickets for help on using tickets.
© 2003 – 2017 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy