Opened 12 years ago
Last modified 8 years ago
#10497 confirmed Bug
Empty lines are removed in enter mode BR - continuation
Reported by: | Jakub Ś | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 4.1.1 |
Keywords: | Cc: |
Description (last modified by )
This is continuation of http://dev.ckeditor.com/ticket/10146#comment:26.
Seems ticket isn't fully fixed. Problem can be reproduced in every browser.
To reproduce:
- Set enter mode to BR
- Clear editor contents and paste below code:
<br /> <br /> <table border="1" cellpadding="1" cellspacing="1" style="width:500px"> <tbody> <tr> <td>Table</td> </tr> </tbody> </table> <br /> <br /> <hr />
- Switch to WYSIWYG and then to source:
<table border="1" cellpadding="1" cellspacing="1" style="width:500px"> <tbody> <tr> <td>Table</td> </tr> </tbody> </table> <hr />
Result: As you can see two BR's were changed into single .
If you were writing an article, created table and wanted to make some space above it then on page save you would end up with single which wasn't intended.
NOTE: This is happening if you use one or two BR's. If you use three BR's then result is "br br nbsp". Assuming that last Br has to be changed into nbsp, should it be "br nbsp" when two BR's are used?
It seems ticket #10146 hasn’t been fully fixed thus this one should be closed and the former reopened.
I have just found that if you paste above code into editor, behaviour will be different in IE. All other browsers change two BR’s into but IE does it in "one by one" style – it removes br and on second switch it turns last br into
Change History (8)
comment:1 Changed 12 years ago by
Status: | new → confirmed |
---|
comment:2 Changed 12 years ago by
Description: | modified (diff) |
---|
comment:3 Changed 11 years ago by
comment:4 Changed 10 years ago by
comment:7 Changed 10 years ago by
#12917 is not a bug and is not a duplicate of this ticket, so it cannot be fixed (see http://dev.ckeditor.com/ticket/12917#comment:4). As for #10497 - I will have a look on it, but as I said - it's a different issue.
Seems this sort of issue was first reported in #7779. It would be nice to know if this change was intended.