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 #5998, comment 3

Timestamp:: Sep 2, 2011, 1:31:30 PM (13 years ago)
Author:: Wiktor Walc
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #5998, comment 3

-                      initial
+                      v1
 ) Use headings to seperate sections, i.e. General Settings, Style Settings, Plugin Settings, SCAYT settings, ouput settings, etc. Use some of those big fancy ASCII dividers people always use, like below or something that will get noticed:
+{{{
 /**************
      SECTION
 ***************/
+}}}
 ) Consistant style... is it CKEDITOR.config.aaa or just config.aaa? Do you specify what the default behavior/value is? How many examples do we really need for each? For instance, I don't know if you're giving me an example of Protected source notation or if that's the defaults. Defaults can serve as examples, they just need to be notated so people aren't double defining things they don't have to.