You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding images or iframes through suneditor to a blogpost or article will give warning in console "A component is contentEditable and contains children managed by React" after viewing that article or blogposts.
...
..
..
Published Article --
This is because when you add image or iframe then an attribute contenteditable=" false" is attached to image component or div of SunEditor. And because of this, warning can be seen in console.
If I remove contenteditable=" false" from source of Suneditor while writing the article and then view that article after publishing then the warning is gone.
@JiHong88 is there a reason why we add contenteditable=" false"?
Conclusion - Adding images or iframes etc. through Suneditor to a blogpost or article will give warning in console "A component is contentEditable and contains children managed by React" after viewing that article or blogposts.
The text was updated successfully, but these errors were encountered:
Adding images or iframes through suneditor to a blogpost or article will give warning in console "A component is contentEditable and contains children managed by React" after viewing that article or blogposts.
...
..
..
Published Article --
This is because when you add image or iframe then an attribute contenteditable=" false" is attached to image component or div of SunEditor. And because of this, warning can be seen in console.
If I remove contenteditable=" false" from source of Suneditor while writing the article and then view that article after publishing then the warning is gone.
@JiHong88 is there a reason why we add contenteditable=" false"?
Conclusion - Adding images or iframes etc. through Suneditor to a blogpost or article will give warning in console "A component is contentEditable and contains children managed by React" after viewing that article or blogposts.
The text was updated successfully, but these errors were encountered: