There is a known issue with Firefox when RadEditor is moved programmatically inside the DOM. To avoid this problem you need to call RadEditor's onParentNodeChanged() method at the end to the DOM manipulations.
To be able to provide more to the point answer we will need more detailed information on the specific scenario? Could you please open a formal support ticket and provide a sample runnable project so we can examine and debug it locally?
the Telerik team