Moving an iframe element (or any of its parent elements) to a new location in the DOM will destroy its contents and event bindings. So unfortunately, moving my CKEditor (using javascript's .appendChild function, or jQuery's .append function, for example) creates problems.
Would any CKEditor expert be able to suggest the most complete way to "repopulate/rebind" the editor after a move, so that the editor once again behaves as expected? I don't believe that I can just re-initialize the textarea again after every move (possibly many). Without guidance, I would also worry about introducing memory leaks.
In my CMS, I could, if necessary, locate every instance of DOM manipulation and destroy my CKEditors beforehand and re-initialize them afterward ... but a simpler solution from those familiar with the CKEditor code would save me a lot of hacking. :)
Thanks.
Would any CKEditor expert be able to suggest the most complete way to "repopulate/rebind" the editor after a move, so that the editor once again behaves as expected? I don't believe that I can just re-initialize the textarea again after every move (possibly many). Without guidance, I would also worry about introducing memory leaks.
In my CMS, I could, if necessary, locate every instance of DOM manipulation and destroy my CKEditors beforehand and re-initialize them afterward ... but a simpler solution from those familiar with the CKEditor code would save me a lot of hacking. :)
Thanks.