ngFor with ng2-ckeditor
See original GitHub issueI use ckditor with ngFor, please see plnkr below. plnkr: https://plnkr.co/edit/Rl4bBoMKOe6xFsduBaaS?p=preview
- when click button
remove me 0
, and then ckeditor break. - when click button
remove me 1
, ckeditor still can use.
Did I miss something?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
ng2-ckeditor set value by typescript - Stack Overflow
In component, I have the following: let group = { 'porcentaje': [setup.porcentaje || '', Validators.compose([Validators.
Read more >ng2-ckeditor/README.md - UNPKG
1, # Angular2 - CKEditor component. 2. 3, Use the [CKEditor (4.x)](http://ckeditor.com/) wysiwyg in your Angular2 application.
Read more >ng2-ckeditor - npm Package Health Analysis - Snyk
ng2 -ckeditor · Angular CKEditor component For more information about how to use this package see README · Security · Popularity · Maintenance...
Read more >How to Work with a Text Editor in an Angular 8 Application
Now install ng2-ckeditor library in this project, to install ng2-ckeditor library use the following command: npm install ng2-ckeditor. Now add ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here is the fix : https://embed.plnkr.co/PqRdBfUdvJ71uUPzY8vG/
You need to include
divarea
plugin :Inline mode is not available atm.
Thanks for reporting this !
Note that using ‘divarea’ does make this error go away BUT the side effect is that now you are using a div for the editor instead of the standard hidden textarea you get with the iFrame of ckeditor out of the box. This means that the CSS styles for your website now apply inside the div (ie. inside the editor area itself). So the user changing things like font style and size could easily get unexpected results.
The correct solution to this problem is to implement the ngOnDestroy hook in your component and destroy the instance of the editor, as shown here.