ckeditor Error code: editor-destroy-iframe

kthorngren

I see the following in the console every time I edit a field using the ckeditor plugin.

[CKEDITOR] Error code: editor-destroy-iframe.
[CKEDITOR] For more information about this error go to http://docs.ckeditor.com/#!/guide/dev_errors-section-editor-destroy-iframe
ckeditor.js:238 Uncaught TypeError: Cannot read property 'isInline' of null
    at CKEDITOR.focusManager.d (ckeditor.js:238)
    at CKEDITOR.focusManager.<anonymous> (ckeditor.js:238)
    at ckeditor.js:28

Doesn't seem to cause any issues. Thought I would post it in case the plugin needs changing or maybe I missed something in my config.

Kevin

allan

I'm not seeing that error I'm afraid. What version of CKEditor are you using? I've got it running 4.4.6 locally.

Thanks,
Allan

kthorngren

I'm using 4.6.2. Its interesting if I change to 4.4.6 I get the following error:

Uncaught TypeError: Cannot read property 'clearCustomData' of null
    at $.detach (ckeditor.js:654)
    at a.CKEDITOR.editor.editable (ckeditor.js:352)
    at a.destroy (ckeditor.js:243)
    at e.<anonymous> (editor.ckeditor.js:89)
    at e.dispatch (jquery-3.1.0.min.js:3)
    at e.q.handle (jquery-3.1.0.min.js:3)
    at Object.trigger (jquery-3.1.0.min.js:4)
    at r.fn.init.triggerHandler (jquery-3.1.0.min.js:4)
    at e._event (dataTables.editor.min.js:75)
    at e._close (dataTables.editor.min.js:71)

I don't get any errors if I disable ckeditor on that field. I have another page using ckeditor with the same version and the same message. Anyway it doesn't seem to be causing any operational issues. I was just checking to see if something immediately stood out as the issue. I'll post back if I can create a test case or find the issue.

Kevin

allan

Nothing immediate I'm afraid. I'll update my copy of CKEditor and let you know what I find.

Allan

allan

It looks like the CKEditor field has to have focus to trigger this error, and I've not been able cause the error in 4.4.6, just in 4.6.2.

If the CKEditor field doesn't have focus, it won't trigger the error.

It looks like CKEditor is using a setTimeout and then running a function without checking to see if it has been destroyed in the mean time or not. Their setTimeout is 1mS, so I can see why they might try to get away with that, but that setTimeout is used at all makes it async, and Editor destroys the field immediately.

Its a CKEditor issue I'm afraid (says me with my teflon suit one ). I'll see if I can produce a simple test case and submit it to them without Editor.

Allan

kthorngren

Its a CKEditor issue I'm afraid (says me with my teflon suit one )

Great, thanks for checking it out. Its only annoying because I usually leave the console open to debug my issues

Kevin

allan

I wish I could debug all my issues in the console ;-)

kthorngren

I wish I could debug all my issues in the console ;-)

Me too!