Not sure what is going on this case. We’ve seen this with the toggle read-only attribute on the demo too:
https://open.esignforms.com/Vaadin7CKEditor/?restartApplication
We’ve even noted that if we toggle the read-only on the second editor in the demo, and then retry on the first editor, it seems to eventually behave as you’d expect. But we don’t really understand if this is something we are doing or just an issue with CKEditor itself.
As you can see, the editor buttons and such seem to show they are in readonly mode, but not the editor region itself, though our code blocks updates when in readonly mode no matter what.
We do not control individual parts for readonly, we just set the editor to readonly or not.
Have you checked what the value of the editor’s readonly attribute is using your browser’s javascript debugger? What is odd to us is that it appears that the editor’s attribute is being set, but the editor itself does not always seem to obey it (though it does for the buttons and such). For example, the command CKEDITOR.instances will show you all editors you have. In our demo page, we have two named ‘editor1’ and ‘editor2’. If you check their read only status, it seems to be correct as we toggle them, yet the editor is not truly behaving as expected:
CKEDITOR.instances.editor1.readOnly
CKEDITOR.instances.editor1.getData() – use this to confirm the editor’s contents as which editor becomes ‘editor1’ is not fixed
What is odd with the demo system, too, is if you load the page, then click the set-read-only, it doesn’t seem to fully work (though the editor icons turn read-only). But if you click inside the editor area without making any changes, then click the set-read-only button, it seems to work fully.
If anybody has an ideas on how to fix, we’ll be happy to incorporate them.