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.

wiki:Features

Context Navigation

Version 5 (modified by Frederico Caldeira Knabben, 14 years ago) (diff)
--

Feature Request Instructions

Avoid Duplicates

Be sure your bug has not been already reported. Use the search to check it, and if you find something related, check if you can add useful comments to discuss about the feature.

Important

Submit different reports for each feature. Don't include more than one feature in the same report.
The "Priority", "Milestone", and "Assign to" fields are reserved to the core team.
Avoid using the "Keywords" field, if you are not 100% sure on what to have there.
For a full guide how to properly report a new feature go to TicketSpecs

Requesting a Feature

Be sure you have read the above instructions before clicking the following link!

If you are not yet registered, take a minute to create a new account. Only authenticated users can create tickets.

Click here to create a new Feature Request

Download in other formats:

Plain Text