-
Notifications
You must be signed in to change notification settings - Fork 33
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
Enable classic editor #6
Comments
This issue will be fixed by upstream issue - ckeditor/ckeditor4#3128 and then we can enable classic editor in the integration. |
I wonder if we should keep If we accept breaking changes during beta phase, we can consider going further, and allow |
Since we had a beta release so far, there is no need for keeping backwards compatibility. It should be enough to explain any changes in the changelog and the blog post. |
CKEditor component is forcing
divarea
plugin. We should should enable use of the classic editor.Currently we are unable to fix this issue. Usage of framed editor in Angular can cause some memory leaks, and console errors. Angular doesn't allow cleanup before elements are removed from DOM,
ngOnDestroy
is called when elements are already removed.There is a feature request on Angular GH: angular/angular#17404
Once it is resolved we can allow the usage of classic editor.
The text was updated successfully, but these errors were encountered: