This document describes how to write a good WebKit bug report. Good bug reports help developers and quality assurance (QA) people decide an appropriate priority and severity for a bug, and increase the chance that a bug will be fixed quickly. The more specific information you can provide, the better.
Please select the WebKit version you were using when the bug occurred, or the closest matching version.
Versions of WebKit that are not part of a Safari release have a +
after the version number, and their version number
is generally higher then the latest released version of WebKit. So, for example, 528+
is an unofficial build of WebKit
that is newer than the 525.x
version that shipped as part of Safari 3.1.2.
If you know the precise cause of a bug (i.e., you've reduced it to a failing test case and know the reason), then you can
assign a bug to a specific component such as CSS
or HTML Editing
.
If, however, there is any doubt in your mind as to the cause of the bug, then file it under New Bugs
. This component
is the place for any bugs whose cause has not yet been determined. Once someone has reduced the bug and knows the cause, then it
will be moved from the New Bugs
component to the appropriate place.
Please select the platform and the OS version that your bug occurred on. If you're running on Mac OS X this would often be platform
Macintosh
and OS Mac OS X 10.5
(Leopard). If you're running on Windows or Linux, please select PC
for platform
and the appropriate entry from the OS field. If your exact system is not listed, please select the closest entry and provide further
details in the description of the bug report.
Normally a QA person or developer will set this, so the bug submitter can leave this at the default value. A number of guidelines and some individual judgment are involved in setting the priority. If you know the bug is a regression, ie. something is wrong which wasn't wrong in previous versions of WebKit, you can set this to P1.
In most cases you should leave this at normal
, but if you are confident that your bug is trivial
or an
enhancement
, it's helpful to specify that value. A QA person or developer will set this to some other value if
appropriate.
Fill in this field with the URL of a page that shows the bug, when possible. If you have created a test case reduction for the bug, please add it to the bug report as an attachment rather than putting it on a web server and listing its URL here. Doing so makes it easier to work on the bug, and can be a first step towards checking in the test case along with the bug fix.
A good summary explains the problem in clear and specific terms, but is often concise enough to fit within the default summary space in Bugzilla. One should be able to tell exactly what a bug is about just by reading the summary.
Tips for a good summary:In this field, write a more detailed explanation of the problem.
Tips for Descriptions:If the bug is specific to one or more of the ports of WebKit (Qt, GTK, Wx, etc), please use any of the valid keywords to tag the bug report accordingly.
If the fix for this bug depends on another bug fix, put the other bug's number here. Otherwise, leave it empty.
If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.