Hello Courtney,

Our team reached a technological limitation related to the specifics of the implementation of the RadEditor component. Its "ContentEditable" attribute is inherited by the parent elements, but it is not explicitly set to "true" on the level of the RadEditor component. For that reason, the recording process is failing to capture your actions against it. I updated the status of this bug report, as we are not currently able to fix this behavior.

In addition to the workaround suggested in my previous message, there is one more from the development side of things. If the developers of the application under test can explicitly set the "ContentEditable" attribute to "true" for the RadEditor component, you will be able to record actions against it. 

I appreciate your feedback and hope the two possible workarounds will help you automate your scenario.

Regards,
Plamen Mitrev
Progress Telerik

Hello Courtney,

I converted your support ticket to this public bug report, because the issue you encountered will need to be investigated further. After that, the team will plan it for future releases and hopefully find a solution. Please vote for and follow this public item for updates and new comments. 

In the meantime, I can suggest a workaround in two steps. For more details see below.

1. Record a click action in the editor. That will enable the editor and show the cursor in it. You can either record a normal "Click" step with enabled SimulateRealClick option, or record a "Desktop mouse left click" step from the context menu. 
2. Add a coded step to type the necessary text in it. The sample code below works best, as it simulates a real user typing from the keyboard.
   

   Manager.Desktop.KeyBoard.TypeText("doubletest", 50, 100, true);

I hope the workaround will be helpful to you. Please do not hesitate to submit new ticket, or add your comment to the bug report.

Regards,
Plamen Mitrev
Progress Telerik