Bulleted list on doesn't work properly for selected lines

[PavelZ]

In fck do: aaaaaaaa
<Shift+Enter>
bbbbbbb
<Shift+Enter>
cccccccc

Place the cursor at the beginning of the document and press <Shift+DownArrow> twice. Two lines of text ale selected. Press "Bulleted list" button. Also the third line (cccccccc) is bulleted

Tested in FCK demo (ver. 2.5 Beta Build 16848) in both FF and IE.

[fredck]

The fact here is that the selection touches the third line too, which seems logic. If you are in the first line and moves two times down, you should expect to be in the third line.

The problem here is the way browsers render the selection in this case. They simply don't render anything in the third line because we have an empty selection there (which would be blinking in a collapsed selection).

[PavelZ]

I would expect the same behaviour as in MS Word.

If the cursor is at the beginnig of the first line and <Shift+DownArrow> is pressed than the cursor is in the second line, but only the first line is selected.

[martinkou]

I've updated the patch because I found a small mistake in the previous patch.

[alfonsoml]

In Firefox 2 and Opera it's fine in my tests

It doesn't seems to work in Safari 3.1 (windows at least)

in IE, (this problem exists before the patch, so it probably should be filed as a different ticket, but just to make it clear that it isn't a regression) the selection is lost after removing the list. It only happens when selecting the lines with the keyboard.

Can you check the Safari thing?

[martinkou]

Confirmed the Safari bug in the previous patch. It is caused by the

if ( FCKListsLib.BlockElements[ currentNode ] )

line towards the end of FCKDomRange::Trim(). It should be FCKListsLib.BlockElements[ currentNode.nodeName.toLowerCase() ] instead.

The IE/remove list issue should belong to another ticket.

[fredck]

I think a simpler solution could be found. Also, probably the correct place to fix is DomRangeIterator, making it ignoring the last paragraph in that case. I'll be working on this.

[julia82]

I'm interested in getting news!

[fredck]

I've been working on a simple fix for this one. I was almost there, bug found out that the current range iterator have some limitations that make it impossible to have a complete fix for it.

I still think that's the way to go for it, but I'm postponing it to V3 so we can calmly rework the range iterator to manage this situation properly.