We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #9993, comment 4

Timestamp:: Feb 1, 2013, 10:03:59 AM (12 years ago)
Author:: tema
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9993, comment 4

-                      initial
+                      v1
 Btw, for almost transparent switching to DIV mode from BR mode you can write a rule for unwrapping every DIV, something like
 {{{
 'div': function(element) { delete element.name; return element; }
+'div': function(element) { delete element.name; element.append(new CKEDITOR.dom.element('br')); return element; }
 }}}
 Also needs a proper condig with the newlines for DIVs.
+Also needs a proper config with the newlines for DIVs.
 If you have some user-generated divs you want to save, you can add an additional step when loading content in CKEditor, which involves adding "class='userDiv'" to every div (can be done with jQuery). Then, unwrap only div without any attributes. I hope I'm explaining correctly. I implemented this, but the code is really tied now.