| 6 | |
| 7 | == report a WebKit bug? == |
| 8 | |
| 9 | If you believe that you have encountered a bug in the WebKit rendering engine, see the page on [http://www.webkit.org/quality/reporting.html reporting bugs]. |
| 10 | |
| 11 | == report a Web Inspector bug? == |
| 12 | |
| 13 | If you believe that you have encountered a bug in the Web Inspector, see the page on [http://www.webkit.org/quality/reporting.html reporting bugs]. You can directly file a bug for the Web Inspector by using this link: [https://webkit.org/new-inspector-bug] |
| 14 | |
| 15 | == report a Safari bug? == |
| 16 | |
| 17 | Safari bugs should be filed in Apple's internal bug tracker at https://bugreport.apple.com/ (free "online" account available [http://connect.apple.com/ here]). |
| 18 | |
| 19 | If you're not sure whether it's a bug in Safari or WebKit, [http://webkit.org/blog/101/back-to-basics/ this blog post] might help. If you're still not sure or have any questions, feel free to [http://webkit.org/contact.html get in touch]. If you accidentally mis-file a bug against Safari or WebKit, don't worry! It will be redirected to the appropriate team by contributors who are better able to triage the bug. |
| 20 | |
| 21 | |
| 22 | == get help with a problem in my JavaScript / CSS / HTML? == |
| 23 | |
| 24 | Most WebKit contributors are focused on fixing bugs and adding features to WebKit and its ports. General web development help is not on-topic in the #webkit IRC channel or mailing lists, and you will probably be ignored. There are many better venues for general help, such as Stack Overflow. |
| 25 | |
| 26 | == get help with a problem in my code that uses JSContext, WebView, WKWebView or WebKit public APIs? |
| 27 | |
| 28 | You should send an email to [http://lists.webkit.org/mailman/listinfo/webkit-help the webkit-help mailing list]. |
| 29 | |
| 30 | == get help with a problem in my code running on an Android device? == |
| 31 | |
| 32 | Android is not a supported platform for WebKit, so it is highly likely that you are not actually running WebKit. Once you've identified the browser engine that you are actually using, you should probably [http://www.chromium.org/for-testers/bug-reporting-guidelines start here]. |