Bug Tracking

Overview

WebKit uses Bugzilla as our primary bug tracking tool, which is hosted at bugs.webkit.org. We use Bugzilla to file bugs, and then we perform code review using GitHub.

Filing a Bug

To file a new WebKit bug please review the steps below.

Create a Bugzilla Account

You’ll need to create a Bugzilla account to be able to report bugs and comment on them.

Check Your WebKit Version

Please ensure you are using latest version of WebKit before filing to verify your issue has not already been resolved. You can download the latest WebKit build from our build archives here.

Search Bugzilla

Please search through Bugzilla first to check if your issue has already been filed. This step is very important! If you find that someone has filed your bug already, please add your comments on the existing bug report.

File the Bug!

If a bug does not already exist you can file a bug here. The Writing a Good Bug Report document 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!

Next Steps

Once your bug is filed, you’ll receive email when it’s updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest WebKit Build Archive and confirm that the fix works for you.

Note: Safari specific bugs should be reported to Apple here.

Editing Bugs

To edit an existing bug on Bugzilla you may need editbug-bits.

Reporting Security Bugs

Security bugs have their own components in bugs.webkit.org. We’re also working on a new policy to delay publishing tests for security fixes until after the fixes have been widely deployed.

Please keep all discussions of security bugs and patches in the Security component of Bugzilla.