AJAX sample fails to populate editing area after subsequent editor instantiations in FF 3

[Damian]

Instances of the editor which have been dynamically created using CKEDITOR.appendTo() fail to properly handle insertHTML(). The first instance of the editor works as expected but when that instance is destroyed and another created in its place, the second instance and all subsequent instances will fail to handle insertHTML().

The behavior can be reproduced by following these steps:

1. Open ​http://ckeditor.com/ckeditor/3.0b/_samples/ajax.html
   
2. Create editor
   
3. Enter content into editing area
   
4. Destroy editor
   
5. Create another editor
   

Expected behavior is that the entered content would be populated in the new editor instance, but it isn't.

The cause has been tracked down to the mode of the editor not being set before setHTML() is called.

A temporary fix for the problem is to update CKEDITOR.editor.prototype.setMode declared in the editingblock plugin and explicitly set the mode (see patch).

The erroneous behavior appears to occur only in Firefox 3.

[Frederico Caldeira Knabben]

We have originally implemented the "mode" property set in the way you have proposed. But, the WYSIWYG mode takes time to get rendered and other parts of the code depends on it to be ready to perform some actions. For that, we had to make the "mode" being set asynchronously.

This new patch considers this "asynchronousity" aspect, ensuring that the data get loaded as soon as the mode is ready.

The patch also fixes an issue in the event system, which came to the light when fixing this ticket.

[Frederico Caldeira Knabben]

Fixed with [3084]. Click here for more info about our SVN system.