Stop using editor.setData() after editor's initialization
#68
Comments
ma2ciek
added a commit
that referenced
this issue
Feb 27, 2019
Fix: Fixed integration with collaboration features by changing the way how the initial data are passed to an editor instance. Previously the `<ckeditor>` component has been using the `editor.setData()` method which produces invalid results in collaboration. Now the initial data are injected directly into the container on which the editor will be created. Closes #68.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It causes the content of the initialized editor is being changed.
There is no problem if only a single user edits the content. But what if two and more users want to edit the editor. Every new connection will reset the editor to the initial state. The entire history of the document will disappear.
We need to find another way to set initialized data.
The text was updated successfully, but these errors were encountered: