Rumen

Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items.

Please, read carefully the information below: The content area of RadEditor is a standard editable IFRAME element which uses the Rich Text Editing engine of the browser under which it operates. The browsers offers a quite limited API and there is not a 100% well working and 100% cross browser solution for implementing editable and non editable areas. Here are the articles that MSDN and Mozilla Development center offer for your scenario:
MSDN: Create and use editable regions with the CONTENTEDITABLE attribute.
Mozilla: https://developer.mozilla.org/en/CSS/-moz-user-select

If you experience any problems, my suggestion is to implement your scenario as a separate solution using an editable DIV element (<div contenteditable="true" style="1px solid red;width:300px;height:300px;">sample content</div> as the editor. If you succeed to implement a fully functional solution using a standard editable DIV, we will help you integrate it into the editor and use the editor content area as a source area.

Best regards,
Rumen
the Telerik team

Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items.

Yes for sure on/off was my understanding.
Concerning what you suggest it certainly will necessitate a long delay to read, understand, test and implement and I have to postpone it, opting for an easier temp solution.
And sharing on this forum is ok for fast information exchange but not for a more long term action.

When I look to ms crm which is our main target at ANT, as Microsoft has limited the browser usage to IE, they use intensively the IE behavior (htc) features to reach this non editable content in a limited editor.
But on our side, we must support also FF and Chrome/Safari, one of the good reasons for working tighly with Telerik.

Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.