﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
6996	destroy() behaves incorrectly if called too soon after instance created	Michael Slusarz		"Example code:

{{{
<html>
 <head>
  <script type=""text/javascript"" src=""ckeditor.js""></script>
 </head>
 <body>
  <textarea name=""test"" rows=""20"" id=""test""></textarea>

  <script type=""text/javascript"">//<![CDATA[
  CKEDITOR.on('instanceReady', function(evt) {
      test_editor.destroy();
  });

  var test_editor = CKEDITOR.replace('test');
  //]]></script>

 </body>
</html>

}}}

Expected behavior:
After the editor instance is destroyed, the original textarea should be restored.

Actual behavior:
The editor instance is destroyed, but the original textarea is not restored.  It still exists, but is hidden via a 'display:none' CSS attribute.

If the destroy() call is delayed at least a second after instanceReady is fired, the textarea is properly restored."	Bug	closed	Normal		General	3.4.3	fixed		wkelley@…
