| | 1 | WebKit, like any large codebase, has more bugs than could ever be fixed. The ones that get fixed are usually the highest priority and/or the easiest to fix. If you want to get your bug fix, you need to up the priority or make it easier to fix. |
| | 2 | |
| | 3 | Ways to up the priority: |
| | 4 | * Add pages that break due to the bug. |
| | 5 | * Add REGRESSION to the title if you are sure it's a regression. |
| | 6 | |
| | 7 | Ways to make a bug easier to fix: |
| | 8 | * If it's a regression, use webkit-nightlies (http://nightly.webkit.org) to identify a regression range. |
| | 9 | * Add a '''small''' reduced test case. If possible have a test case the doesn't require human interatction, i.e., all you have to do is load the page to see the bug. |
| | 10 | |
| | 11 | It may also help to CC people with experience in the relevant part of the codebase, but that just ensures the bug is on their radar. |
