Version 12 (modified by Anna Tomanek, 9 years ago) (diff)

Minor updates to make it consistent with!/guide/dev_issues_tracker

Bug Reporting Instructions

If you found a bug in CKEditor, please follow the instructions outlined below.

Reproduce on Demo Page and/or Nightly Build

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:

The demo page is always running the latest CKEditor release, so if you cannot reproduce your issue there, update your editor installation first. Please note that if the problem was fixed in one of the releases that succeeded the version you are using, you will need to upgrade your CKEditor installation as we do not backport fixes.

CKEditor is in active development, so there is a chance that we have already fixed your issue in the current code base. You should thus also test it our last "Nightly Build":

Avoid Duplicates

Before you file a new ticket, make sure your bug has not been reported yet. Use the search field (at the top of this page) to check it.

Required Information

Please provide the following when reporting new issues. The more information you provide, the quicker the problem 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 invaluable.
  • Browser name and OS - Your computer configuration, OS, browser name and version.
  • Editor configuration – Your editor version, integration method, editor build (you can attach your build-config.js file). If you are using a custom build or the problem only occurs in some specific editor packages, this information is crucial for us.
  • Screenshot - For interface-related issues an image speaks more than thousands of words.
  • Sample data - For content-related issues 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 issue. This is the best way to show us the problem and make it quicker to solve.

Important Notes

When filing an issue, please bear these important things in mind:

  • Submit separate reports for each issue. Do not include more than one issue in the same report.
  • The "Priority", "Milestone", and "Assign to" fields are reserved for the core development team.
  • Avoid using the "Keywords" field if you are not 100% sure what to put there.
  • Make sure you are using the latest version of CKEditor. Maybe your bug has already been fixed.
  • The "Version" field should be used to point the version where the problem occurred for the first time. If you cannot assess it, just set it to the version in which you are experiencing the issue.
  • For a full guide on how to properly report a new bug go to the TicketSpecs page.

Reporting a Bug

Before clicking the following link, make sure you have read the instructions above!

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

Click here to create a new Bug Report

© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy