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 you can provide, the better.
--
+
- 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 is the WebKit version that shipped with Mac OS X 10.4 (Tiger). Locally-built versions - of WebKit have a + after the most recent official build number. So, for example, 412+ is a locally-built version of WebKit - that's newer than the 412 version shipped with Tiger.
++ 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. +
+ + - 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 @@ -39,13 +46,14 @@ you can provide, the better.
-
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).
+ and OS Mac OS X 10.3 (Panther) or Mac OS X 10.4 (Tiger). -
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.
+ 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. -
@@ -65,7 +73,7 @@ you can provide, the better.
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 suummary: + 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
@@ -97,7 +105,7 @@ you can provide, the better.
Blocks
If this bug blocks another bug from being fixed, put the other bug's number here. Otherwise, leave it empty.
-