Permission denied on setReadOnly in IE

[kphung]

I am getting a permission denied error only in IE browser, on setReadOnly(). Looking deeping in ckeditor.js, it looks like the editable HTML body element is giving the permission denied error.

I've tried on FireFox and Chrome and both works fine.

[kphung]

Replying to kphung:

I am getting a permission denied error only in IE browser, on setReadOnly(). Looking deeper* in ckeditor.js, it looks like the editable HTML body element is giving the permission denied error.

I've tried on FireFox and Chrome and both works fine.

[Jakub Ś]

First of all you should check this issue with latest CKEditor 4.5.1 or at least with 4.4.8.
Second is that I have not been able to reproduce this issue in default CKEditor.

Please provide reduced HTML file (with css and js files if needed) which can be put in samples folder of default CKEditor and will show this issue.
If this is happening only when CKEditor is integrated into your application then please either fix this problem on your side or please try to isolate it so that it can be reproduce in sole CKEditor.

[kphung]

I was able to narrow the problem down. I'm using jquery deferred to call the setReadOnly() after the editor has been initialized and is ready. So, I have

editor.on('instanceReady', function () {

_ckeditorInitDeferred.resolve(editor);

});

When using deferred to call setReadOnly(), that was giving me the 'Permission denied' error in IE.

However, if I have setReadonly() in the function on instanceReady instead, that does not give me the error message.

editor.on('instanceReady', function () {

editor.setReadOnly();

_ckeditorInitDeferred.resolve(editor);

});

I searched and wasn't able to find any explanation for why this works and when using jquery deferred I get permission denied. Have you encountered something like this before ?

[kphung]

I also upgraded to version 4.5.1 and I still get that behaviour in my previous comment

[kphung]

Are there any updates to this behaviour ?

[Jakub Ś]

Have you encountered something like this before?

We haven't but, IE throws access denied in many cases. It is possible that there is something wrong with JQuery which touches sensitive data in IE or simply that you have made a mistake in your implementation.

We need reduced and working sample in order to see the issue.

I'm closing this ticket as invalid but if you provide working sample (HTML file with JS that I can put in samples folder of default editor and will see the problem) we will consider reopening it.