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.
| initial | v1 | |
|---|---|---|
| 1 | 1 | Hello. |
| 2 | 2 | Thank you for the reported issue. Currently we're looking for the solution. |
| 3 | The behavior w |
|
| 3 | The behavior will be fixed in the upcoming release. | |
| 4 | 4 | The CKEditor's markup won't be affected by SCAYT for the described steps. |
