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.

  1. Version

    Please select the WebKit version you were using when the bug occurred, or the closest match. 312 is the WebKit version that shipped with Mac OS X 10.3.9. 412 up to 417.9 are the WebKit versions that shipped with Mac OS X 10.4 (Tiger) and it's updates.

    Locally-built versions of WebKit have a + after the build number, and their build number is generally higher then the latest release version. So, for example, 420+ is a locally-built version of WebKit that's newer than the 417.9 version that shipped with the latest update of Tiger.

  2. Component

    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.

  3. Platform and OS

    Please select the platform and the OS version that your bug occurred on. Typically this would be platform Macintosh and OS Mac OS X 10.3 (Panther) or Mac OS X 10.4 (Tiger).

  4. Priority

    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.

  5. Severity

    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.

  6. URL

    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.

  7. Summary

    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:
    • include the domain of the page that shows the bug (especially if it's an important site)
    • if the bug is a crash, note this and note whether or not the crash is reproducible
    • if you have tested and verified that this is a regression from a previous version of WebKit, prepend "REGRESSION" to the summary
    • if you know between which versions of WebKit the regression occurred, add this to the summary after REGRESSION (i.e., "REGRESSION (125-408)")

  8. Description

    In this field, write a more detailed explanation of the problem.

    Tips for Descriptions:
    • Please do not include more than one bug in one bug report.
    • If you can only reproduce the problem on a version of WebKit that you built yourself, include the date that you checked out the source code.
    • If there is no simple URL to a page that shows the bug (for instance, you have to click through multiple pages for the bug to occur), then describe the exact navigation required to reach the page where the bug occurs. Don't just say "go to the forums"; use detailed steps.
    • Look at Console and include any messages that might be relevant in the bug.
    • Include the backtrace if you get a crash, if possible. File the bug first and then add the backtrace as an attachment.
    • Include a screenshot for visual bugs. If the problem isn't very obvious, include a single screenshot which shows both correct and incorrect renderings, for example Safari and another browser such as Firefox or Mac IE. Use or cmd-shift-4 and grab as small an area as possible that demonstrates the problem. Then attach the screenshot to the bug.
    • Be as specific as possible. For instance, if you're describing a problem that occurs while scrolling, note in the bug whether you're scrolling with arrow keys, arrow buttons, scroll thumb, clicking above or below the thumb, scroll-wheel mouse, etc.

  9. Depends on

    If the fix for this bug depends on another bug fix, put the other bug's number here. Otherwise, leave it empty.

  10. Blocks

    If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.