Reporting Bugs

You have found a bug? Here are 5 steps to getting it fixed!

  1. Check your WebKit version
    To make sure you're not wasting your (and our) time, you should be using the latest version of WebKit before you file your bug. You should run at least Mac OS X 10.3.9 before filing bugs. Your WebKit version should be 312 or higher if you are on Panther and 417 or higher if you are on Tiger. If you're running Mac OS X 10.4, you could also download the latest nightly build to be sure you have the latest version. If you've done this and you still experience the bug, go ahead to the next step.
  2. Search Bugzilla
    Now that you have the latest WebKit version and still think you've found a WebKit bug, search through Bugzilla first to see if anyone else has already filed it. This step is very important! If you find that someone has filed your bug already, please go to the next step anyway, but instead of filing a new bug, comment on the one you've found. If you can't find your bug in Bugzilla, go to the next step.
  3. Create a Bugzilla account
    You will need to sign up for a Bugzilla account to be able to report bugs (and to comment on them). Once you have an account you can report bugs on any product on WebKit is one of the individual products listed in Bugzilla, and all of our bugs can be classified in various components under the WebKit product. If you have registered, proceed to the next step.
  4. File the bug!
    Now you are ready to file a bug on the WebKit product. The Writing a Good Bug Report document (also linked in the sidebar) gives some tips about the most useful information to include in bug reports. The better your bug report, the higher the chance that your bug will be addressed (and possibly fixed) quickly!
  5. What happens next?
    Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.

To report bugs in Safari, or WebKit bugs that may contain confidential information, please use