= Bug Reporting Instructions =

== Avoid Duplicates ==

Be sure your bug has not been already reported. Use the search field (at the top of this page) to check it.

You should also test it at our last "[wiki:SVN#NightlyBuild Nightly Build]":[[BR]]
http://nightly.ckeditor.com/demo

== Required Information ==

Please provide the following when reporting new bugs. As more info you provide, as quicker the bug may be solved:

 * '''Descriptive summary''' : A "right to the point" phrase.
 * '''Steps to reproduce''' : This is the most important thing. We are not able to fix a bug if we can't see it with our own eyes. A numbered list of actions to reproduce the issue is quite useful.
 * '''Browser name and OS''' : You computer configuration, OS, browser name and version.
 * '''Screenshot''' : For interface related issues, an image says 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.

== Important ==

 * '''Submit different reports for each bug'''. Don't include more than one bug 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.
 * Be sure you are '''using the latest version of CKEditor'''. Maybe your bug has already been fixed.
 * For a full guide how to properly report a new bug go to [wiki:TicketSpecs]

== Reporting a Bug ==

{{{
#!html
<div style="color:red">
<b>Be sure you have read the above instructions before clicking the following link!</b>
</div>
}}}

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

[/newticket?type=Bug Click here to create a new Bug Report]

----