Fixed breaking code when creating and destroying the editors

[bleadof]

http://jsfiddle.net/Z4dBN/4/

This is the setup I've encountered the JS errors with and my patch will get rid of those errors. It's a quick patch and I haven't dug deeper into why errors happen, but I know for sure it's because I'm destroying and attaching editors very quickly. During this some events are lagging a bit behind and the editor.element reference is already gone when some of the events are triggered.

I don't know why the editor doesn't show up on the fiddle, it does on my computer, but I think this fiddle still points out the problem.

If you want me to change the patch so that the element reference is checked elsewhere, I'm more than happy to do so.

[Reinmar]

First of all - I'm sorry for the delay. 8 months is a much too long time for a response ;).

From the changes you proposed I conclude that you destroy editor before configuration loads. There are couple of other moments when editor cannot be destroyed and we are planning to make necessary architecture changes to avoid these situations. But it has to be a general fix and the patch proposed by you just prevents from error being thrown. So for now, let's not make the code more blurry.