Ticket #18 (closed Bug: fixed)

Opened 5 years ago

Last modified 5 years ago

IE: Enter after Shift+Enter eats the paragraph

Reported by: alfonso@… Owned by: FredCK
Priority: Normal Milestone: FCKeditor 2.4
Component: UI : Enter Key Version:
Keywords: Cc:

Description (last modified by FredCK) (diff)

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

comment:1 Changed 5 years ago by FredCK

  • Milestone set to FCKeditor 2.4

comment:2 Changed 5 years ago by FredCK

  • Owner set to FredCK
  • Status changed from new to assigned
  • Description modified (diff)
  • Summary changed from Enter after Shift+Enter eats the paragraph (IE) to IE: Enter after Shift+Enter eats the paragraph

comment:3 Changed 5 years ago by FredCK

  • Status changed from assigned to closed
  • Resolution set to fixed

Fix committed to trunk.

comment:4 Changed 5 years ago by alfonso@…

  • Status changed from closed to reopened
  • Resolution fixed deleted

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 5 years ago by FredCK

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 5 years ago by FredCK

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 5 years ago by FredCK

  • Status changed from reopened to closed
  • Resolution set to fixed

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 – 2011 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy