ckeditor4-vue
ckeditor4-vue copied to clipboard
ckeditor
Vue 3 support
Vue 3 will be probably released in Q1 2020. Once it's in a stable version, we should consider upgrading integration, so it's working with the latest version or create separate integration if not possible due to breaking changes.
For now, let's just wait until Vue 3 release to find out the best solution.
Vue 3 stable version is planned for Q2 2020 (https://github.com/vuejs/vue/projects/6) so we should just keep an eye on it and check support when stable version available.
Vue 3 has been released - https://news.vuejs.org/issues/186
Let's check if there are some breaking changes.
It seems it doesn't work in IE11 for now (https://github.com/vuejs/vue-next/releases/tag/v3.0.0):
Migration and IE11 Support
We have pushed back the migration build (v3 build with v2 compatible behavior + migration warnings) and the IE11 build due to time constraints, and are aiming to focus on them in Q4 2020. Therefore, users planning to migrate an existing v2 app or require IE11 support should be aware of these limitations at this time.
Anyway, maybe it will be a good moment to introduce separate tests for v2 and v3 (similar to what we have reported in React - ckeditor/ckeditor4-react#121)? We need some way to test integration in v3 and using existing tests (or similar ones) could be a good approach.
It seems CKE5 started doing some stuff related to supporting different Vue versions:
- https://github.com/ckeditor/ckeditor5-vue
- https://github.com/ckeditor/ckeditor5-vue2
In case anyone's looking for a temporary fix, to run their editor until official support arrives for Vue 3, you can try https://github.com/mayasabha/ckeditor4-vue3 . It works with the new v-model system of Vue 3. There are a few bugs such as the parent element for the editor seems to remain in the display: none; state after the editor is initialiazed. A quick workaround for this is to add a .style.display = 'block'; to the parent component's mounted method.
Given there being no action on this request at all, and the CKEditor 4 End Of Life being a few days away, I take it that this is going to be a "won't fix" on the CKEditor team's end?
