v3.0.1

Bug fixes

• Synchronize the editor content after the editor is ready. Closes #21. (commit)

v3.0.0

BREAKING CHANGES

• Due to introducing the lock mechanism for the Editor#isReadOnly property, the <CKEditor> component uses the new way of enabling the read-only mode in the editor. The component requires an instance of CKEditor 5 in version 34 or higher. See ckeditor/ckeditor5#10496.

Other changes

• Aligned the <CKEditor> component API to use the new lock mechanism when enabling/disabling the read-only mode. (commit)
• Bumped Karma test runner to v6.x. Closes #18. (commit)

v2.0.0

BREAKING CHANGES

• Upgraded the minimal versions of Node.js to 14.0.0 due to the end of LTS.

Other changes

• Updated the required version of Node.js to 14. Closes #10972. (commit)

v1.0.5

Bug fixes

• When using the <CKEditor> component with an unsupported version of Vue.js, the component will display an error. Closes #6. (commit)

v1.0.4

Starting from this version, the CKEditor 5 WYSIWYG editor component is compatible with Vue.js 2.x only. For Vue.js 3.x, check the dedicated @ckeditor/ckeditor5-vue component.

v1.0.3

Bug fixes

• The editor should not slow down with lots of content when using the integration. Closes #153. (commit)

MINOR BREAKING CHANGES ℹ️

• The reference to the CKEditor 5 instance previously available under the instance property of the component (data) is now private ($_instance). We recommend you use the ready component event to access the editor API instead.

v1.0.2

Bug fixes

• The #input event should be fired immediately despite being debounced to prevent race conditions. Closes #149. (commit)

v1.0.1

Bug fixes

• Editor config defined in the component should not be mutable. Closes #101. (42651e3)

v1.0.0

Bug fixes

• config.initialData should be used to set the initial state of the editor instead of unsafe innerHTML. Closes #51. (950b49a)

v1.0.0-beta.2

Bug fixes

• Improved performance when editing large content. Debounced the component #input event. Closes #42. (dfaee36)
• The data initialization should not break collaboration. Instead of using editor.setData(), the initial content is now set via innerHTML of the source element. Closes #47. (6f821fa)