Opened 16 years ago

Closed 15 years ago

#309 closed Bug (fixed)

Span with nonbreaking space added to button when adding paragraph break in IE

Reported by: Mike Nicholls Owned by: Frederico Caldeira Knabben
Priority: Normal Milestone: FCKeditor 2.6
Component: UI : Enter Key Version: FCKeditor 2.4.1
Keywords: Review+ Cc:


Using IE, switch to source view, paste this code and then switch back to WYSIWYG view:


Placing the cursor between the two buttons and pressing enter to add a paragraph break adds a span with a non-breaking space inside the second button:


Attachments (2)

309.patch (891 bytes) - added by Martin Kou 15 years ago.
Proposed patch for fixing #309.
309_2.patch (1.3 KB) - added by Frederico Caldeira Knabben 15 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 16 years ago by Frederico Caldeira Knabben

Component: GeneralUI : Enter Key
Keywords: Confirmed IE added; button paragraph p span nbsp removed
Milestone: FCKeditor 2.6

Confirmed with IE6. With FF, we have a strange behavior which deserves a dedicated ticket.

In IE, we actually have an error when working with the SVN dev code. It seams that the remaning span is a marker for the selection.

comment:2 Changed 15 years ago by Martin Kou

Owner: set to Martin Kou
Status: newassigned

Changed 15 years ago by Martin Kou

Attachment: 309.patch added

Proposed patch for fixing #309.

comment:3 Changed 15 years ago by Martin Kou

Keywords: Review? added; Confirmed IE removed

Took a while to figure out, but the fix for this is surprisingly simple.

comment:4 Changed 15 years ago by Martin Kou

The problem here comes from the FCKDomRange.MoveToElementEditStart() call in the enter key logic - it tries to move the caret into the button in the newly split paragraph. It is not possible to move the caret into a button in IE, however. Adding the BUTTON tag into FCKListsLib.EmptyElements() prevents MoveToElementEditStart() from moving the caret into the button.

comment:5 Changed 15 years ago by Frederico Caldeira Knabben

Keywords: Review- added; Review? removed
Owner: changed from Martin Kou to Frederico Caldeira Knabben
Status: assignednew

Your analysis is perfect Martin. The implementation has some problems though.

Adding "button" to EmptyElements is a dirty hack to fix this ticket. The comment right above the EmptyElements definition is quite precise: Elements marked as empty "Empty" in the XHTML DTD. The button element is not marked as empty, so it should not be added to that list. By doing so, we could easily have collateral effects. For example, it opens the possibility of having self-closing <button /> tags in the output, which is wrong.

Changed 15 years ago by Frederico Caldeira Knabben

Attachment: 309_2.patch added

comment:6 Changed 15 years ago by Frederico Caldeira Knabben

Keywords: Review? added; Review- removed
Status: newassigned

The proposed solution uses InlineNonEmptyElements instead of EmptyElements in the MoveToElementEditStart. It should satisfy the needs of MoveToElementEditStart.

comment:7 Changed 15 years ago by Martin Kou

Keywords: Review+ added; Review? removed

comment:8 Changed 15 years ago by Frederico Caldeira Knabben

Resolution: fixed
Status: assignedclosed

Fixed with [1404]. Click here for more info about our SVN system.

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