Hi,

We have an issue with the ordered/unordered list options in the editor. Adding an unorderedlist causes the entire text in a TD element to be intended, not the specific text where the cursor is placed or text is selected. 

Reproduceable steps:
- Go to the demos: http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx
- Paste the following text into the editor:

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Cum sociis natoque penatibus et magnis dis parturient montes

- Put your cursor at beginning ot the second paragraph (at beginning of the word Cum)
- Press on the unordered list button

The unordered bullet will be added at beginning of the first paragraph. 
This is an bug issue for us because of high count people working with it, so it's URGENT for us.

Are you aware of this issue?

Kind regards,
Jelle de Boer

Tested in Chrome version 41.0.2272.101, happens in FireFox and IE as well.

Works fine when the paragraph is seperated with P tag:
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit.</p>
<p>Cum sociis natoque penatibus et magnis dis parturient montes</p>

Not with <BR> tags:
Lorem ipsum dolor sit amet, consectetur adipiscing elit.<br /><br />
Cum sociis natoque penatibus et magnis dis parturient montes

Hi Jelle,

This behavior is expected.

Block commands like the InsertList command work on block elements and not with line breaks, just like in MS Word. This is why the default NewLineMode property of the editor is now P, so it generates paragraphs and the user can work properly with them. As for pasted content - it is up to the browser to provide the HTML and this greatly depends on the source of the content and the browser, and RadEditor has virtually no control over that.

You can read more about the current commands' behavior and a way to get an old version of the commands in the following article: http://www.telerik.com/help/aspnet-ajax/editor-inline-and-block-commands-behavior-change.html.

Regards,

Marin Bratanov
Telerik

It's clear now!
With updating from 2012 version to Q3 2014, we were not aware about this switch.
Very happy with the scripts to rollback the functionality and keep the new version of the editor. 
We will test it!