3 ms·

I've had quite good luck getting responses to my bug reports, but it requires active lobbying. You need to figure out whether it's a Chrome bug or a WebKit bug

I've had quite good luck getting responses to my bug reports, but it requires active lobbying. You need to figure out whether it's a Chrome bug or a WebKit bug. If it's a WebKit bug, file a link in WK's Bugzilla and link to it in a crbug issue. Then, go on IRC and pester the person responsible for fixing that component. It's helpful if you can go through the source and propose where the bug might be. Examples: https://bugs.webkit.org/show_bug.cgi?id=32303 https://bugs.webkit.org/show_bug.cgi?id=32303 https://bugs.webkit.org/show_bug.cgi?id=35472 https://bugs.webkit.org/show_bug.cgi?id=35472 I hate to pester people who are already working on other things, but some bugs just need to be fixed at the browser level.

lizzard 14y ago
This is a good approach! Doing a little work to narrow down the scope of the bug and where it belongs can go a long way towards bringing it to the right developer's attention. It also helps to attach a reduced test case and as much information as you can glean about the bug so that it can be reproduced. And as you say, there is a point as well to go on IRC and ask. :D
- bsimpson 14y ago
  Yes, reductions definitely help.