Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#18 closed Bug (fixed)

IE: Enter after Shift+Enter eats the paragraph

Reported by: Alfonso Owned by: Frederico Caldeira Knabben
Priority: Normal Milestone: FCKeditor 2.4
Component: UI : Enter Key Version:
Keywords: Cc:

Description (last modified by Frederico Caldeira Knabben)

Testing the enter key in IE:

  • Go to end of text, press enter a new paragraph starts;
  • Type some letters or words and press shift+enter, a new line starts;
  • Type a little more and press enter to start a new paragraph, now the current paragraph simply disappears.

Blocks #1

Change History (7)

comment:1 Changed 12 years ago by Frederico Caldeira Knabben

Milestone: FCKeditor 2.4

comment:2 Changed 12 years ago by Frederico Caldeira Knabben

Description: modified (diff)
Owner: set to Frederico Caldeira Knabben
Status: newassigned
Summary: Enter after Shift+Enter eats the paragraph (IE)IE: Enter after Shift+Enter eats the paragraph

comment:3 Changed 12 years ago by Frederico Caldeira Knabben

Resolution: fixed
Status: assignedclosed

Fix committed to trunk.

comment:4 Changed 12 years ago by Alfonso

Resolution: fixed
Status: closedreopened

While testing the anchor code I had again the problem, I tested the trunk and it also failed there so it wasn't a bad merge in the branch.

comment:5 Changed 12 years ago by Frederico Caldeira Knabben

I'm completely reviewing the Enter Key Handler for IE. IE's TextRange seams unusable. I'm implementing the W3C DOM Range specifications for IE. I believe we'll have a much better implementation in this way.

So for a while, let's stay on hold with the Enter Key tests on IE. Unfortunately we haven't started working with branches when I've started this development. I hope I'll be committing an update soon.

comment:6 Changed 12 years ago by Frederico Caldeira Knabben

I've just disabled the Enter Key handler by default. It will be available on sample12.html only, so we can continue with other developments without being interfered.

comment:7 Changed 12 years ago by Frederico Caldeira Knabben

Resolution: fixed
Status: reopenedclosed

The new implementation, just committed, doesn't present this behavior. We should now restart and intensive testing over this new feature. This is the only thing blocking us to release the 2.4.

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