Bug Report Guidelines
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 @@ -47,6 +21,19 @@ you can provide, the better.locally-built version of WebKit that's newer than the 417.9 version that shipped with the latest update of Tiger. +
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 @@ -119,6 +106,6 @@ you can provide, the better.
If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.