Opened 17 years ago

Closed 17 years ago

Last modified 14 years ago

#208 closed Bug (duplicate)

IE remove <br /> after any ending tag

Reported by: zheng@… Owned by:
Priority: Normal Milestone:
Component: General Version: FCKeditor 2.4
Keywords: Cc:


I found out that doesn't matter what you do right after any closing tags (ex: </font>, </strong> ....) <br /> is removed. For Example: In Editor mode Typing following FCKEditor Give 'FCK' A <strong> tag, then right after K "SHIFT-ENTER" Now switch to Source View It should give this => <p><strong>FCK</strong><br>Editor</p> but is actually gives <p><strong>FCK</strong>Editor</p> without <br /> I tried with all different kinds of the closing tags ex: </font>, </em>, </u>.....

Attachments (1)

FCK remove br.avi (132.1 KB) - added by zheng@… 17 years ago.
FCK remove <br /> after any closing tags

Download all attachments as: .zip

Change History (4)

comment:1 Changed 17 years ago by Frederico Caldeira Knabben

Component: UI : Source ViewGeneral
Priority: HighNormal
Resolution: duplicate
Status: newclosed

DUP of #90

comment:2 Changed 17 years ago by zheng@…

Resolution: duplicate
Status: closedreopened

Tried fix in #90(which redirect to #168). It doesn't work. For All IE Goto "Shift-Enter" right after 'sample text' and before '.' Looks like it did go down one line. However, switch to source view you will not see <br /> after 'sample text</strong>' Then switch back to editor view, it is back to one line

I tried "Shift-Enter" after all closing tags (</font>,</u>...), <br /> will not be there.

Changed 17 years ago by zheng@…

Attachment: FCK remove br.avi added

FCK remove <br /> after any closing tags

comment:3 in reply to:  2 Changed 17 years ago by Frederico Caldeira Knabben

Resolution: duplicate
Status: reopenedclosed

Replying to

I think you are a little bit confused. Let me try to explain some things.

Tried fix in #90 (which redirect to #168).

You must pay attention for the Trac linking syntax. The # symbol indicates a "Ticket". So, #90 points to the "Ticket 90", while #168 points to the "Ticket 168".

At #90, you can find the comment "Fixed with [168]". Note that the number 168 is not prefixed with a #, but is inside square-brackets. The square-brackets instead represents a link to a SVN commit changeset. So, [168] is not pointing to ticket 168, but to "Changeset 168".

Actually it is enough to click on the links to see the difference.

It doesn't work. For All IE Goto

The online demo is running the latest public release, which means version 2.4 as today. The fix proposed in #90 has been committed to the SVN instead, and will be available only in the next public release, possibly version 2.4.1.

For now, the fix can be retrieved from the SVN or from our nightly build. This is why you may also find the following comment at #90: "Click here for more info about our SVN system".

I confirm you this bug has already been fixed.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy