So you found a bug? Here are 5 steps to getting it fixed:
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. First, you should download the latest WebKit build archive 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.
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.
You’ll need to create a Bugzilla account to be able to report bugs and to comment on them. If you’ve registered, proceed to the next step.
Now you’re ready to file a bug on the WebKit product. 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!
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.