#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 )
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 18 years ago by
Milestone: | → FCKeditor 2.4 |
---|
comment:2 Changed 18 years ago by
Description: | modified (diff) |
---|---|
Owner: | set to Frederico Caldeira Knabben |
Status: | new → assigned |
Summary: | Enter after Shift+Enter eats the paragraph (IE) → IE: Enter after Shift+Enter eats the paragraph |
comment:3 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 18 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
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 18 years ago by
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 18 years ago by
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 18 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
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.
Fix committed to trunk.