You would have to be more specific about your CKEditor configuration.
It's quite possible this is Advanced Content Filter at work -- your editor configuration simply does not allow for styles in <div> elements.
See the demos on our website:
In Standard preset <div> feature is not supported, so even if you add a <div> element in source mode, it will be filtered out when you switch to WYSIWYG view.
In Full preset <div> feature is supported, you can click the Div Container button, configure this element's properties, including CSS styles (or add them in source mode) and they will be preserved.
By the way, I do recommed you upgrade to the latest version, apart from loads of new features added, a security fix was also included in CKEditor 4.4.3.
You would have to be more
You would have to be more specific about your CKEditor configuration.
It's quite possible this is Advanced Content Filter at work -- your editor configuration simply does not allow for styles in <div> elements.
See the demos on our website:
By the way, I do recommed you upgrade to the latest version, apart from loads of new features added, a security fix was also included in CKEditor 4.4.3.
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Hi, Anna
Hi, Anna
I find that if I use config.allowedContent = true in config.js, <div> will apply the css code change.
Is there any Side Effects for using this config?