Bug Reporting Instructions
If you feel you found a bug in CKEditor, we will be grateful for letting us know.
Reproduce on Demo Page
To eliminate the chance that the issue might be caused by some third-party software or your customizations, try to reproduce the bug on the demo page first: http://ckeditor.com/demo
Before you file a new ticket, make sure your bug has not been already reported. Use the search field (at the top of this page) to check it.
Please provide the following when reporting new bugs. The more information you provide, the quicker the bug may be solved:
- Descriptive summary : A "right to the point" phrase that best summarizes the issue that you are having.
- Steps to reproduce : This is the most important thing. We are not able to fix a bug if we cannot see it with our own eyes. A numbered list of actions to reproduce the issue is quite useful.
- Browser name and OS : Your computer configuration, OS, browser name and version.
- Screenshot : For interface related issues an image speaks more than thousands of words.
- Sample data : For content related bugs please attach a sample file from which we can get the text for testing.
- Test case file : If possible, attach a Test Case file showing the bug. This is the best way to show us the problem, making it quicker to solve it.
While filing the bug please bear these important things in mind:
- Submit different reports for each bug. Do not include more than one bug in the same report.
- The "Priority", "Milestone", and "Assign to" fields are reserved to the core development team.
- Avoid using the "Keywords" field if you are not 100% sure on what to put there.
- Make sure you are using the latest version of CKEditor. Maybe your bug has already been fixed.
- For a full guide on how to properly report a new bug go to the TicketSpecs page.
Reporting a Bug
If you are not yet registered, take a minute to create a new account. Only authenticated users can create tickets.