Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vue 3 support #6

Open
jacekbogdanski opened this issue Dec 17, 2019 · 8 comments
Open

Vue 3 support #6

jacekbogdanski opened this issue Dec 17, 2019 · 8 comments
Labels
status:confirmed An issue confirmed by the development team. type:feature A feature request.
Milestone

Comments

@jacekbogdanski
Copy link
Member

jacekbogdanski commented Dec 17, 2019

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.

@jacekbogdanski jacekbogdanski added type:feature A feature request. status:confirmed An issue confirmed by the development team. and removed enhancement labels Feb 7, 2020
@jacekbogdanski jacekbogdanski modified the milestone: 1.0.0 May 12, 2020
@f1ames
Copy link
Contributor

f1ames commented May 14, 2020

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.

@f1ames f1ames added this to the Next milestone May 27, 2020
@jacekbogdanski
Copy link
Member Author

Vue 3 has been released - https://news.vuejs.org/issues/186

Let's check if there are some breaking changes.

@f1ames
Copy link
Contributor

f1ames commented Sep 25, 2020

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.

@f1ames
Copy link
Contributor

f1ames commented Nov 19, 2020

It seems CKE5 started doing some stuff related to supporting different Vue versions:

@apoorvpal01
Copy link

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.

@mkarkash
Copy link

Any updates on how its going?

@KarolDawidziuk
Copy link
Contributor

Hi, @muratkarsh

Currently, we don't have any ETA for this task.

@mbabker
Copy link

mbabker commented Jun 26, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:confirmed An issue confirmed by the development team. type:feature A feature request.
Projects
None yet
Development

No branches or pull requests

6 participants