1,926
edits
QA/Talkback/FAQ: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== | == What does it mean when I see the following error when submitting a crash incident: "The Agent is unable to connect to the server. Please check your Proxy Server settings or try again later."? == | ||
This error message is misleading. It does not always indicate a proxy related problem or mean that your incident has not been submitted to the Talkback Server. For more info, see [https://bugzilla.mozilla.org/show_bug.cgi?id=210251#c70 Bug 210251, Comment 70]. | This error message is misleading. It does not always indicate a proxy related problem or mean that your incident has not been submitted to the Talkback Server. For more info, see [https://bugzilla.mozilla.org/show_bug.cgi?id=210251#c70 Bug 210251, Comment 70]. | ||
== | == What data is sent with my crash incident? == | ||
There are a number of things that are included in the crash incident that is submitted to us. For more info, see [http://www.mozilla.org/quality/qfa.html the Old QFA page on mozilla.org] (a bit outdated, but it shows you how to check the data to be send with the Talkback Client). | There are a number of things that are included in the crash incident that is submitted to us. For more info, see [http://www.mozilla.org/quality/qfa.html the Old QFA page on mozilla.org] (a bit outdated, but it shows you how to check the data to be send with the Talkback Client). | ||
== | == What additional information should I specify when submitting a crash incident? == | ||
Aside from the data collected automatically by Talkback, the crash dialog allows you to specify your email address, a URL, and comments about your crash. It is important that you provide us with as much useful information as you can to improve our ability to debug the issue. This includes the website you were visiting, any plugins or extensions you think might be related to the crash, what you were doing, etc. If you have been able to crash consistently, exact steps to reproduce the crash would be ideal! | Aside from the data collected automatically by Talkback, the crash dialog allows you to specify your email address, a URL, and comments about your crash. It is important that you provide us with as much useful information as you can to improve our ability to debug the issue. This includes the website you were visiting, any plugins or extensions you think might be related to the crash, what you were doing, etc. If you have been able to crash consistently, exact steps to reproduce the crash would be ideal! | ||
* NOTE: If you submit your email address, it will be kept private (only Mozilla will be able to see that data). Personal information like IP and email addresses will not show up in public Talkback reports or query results. | * NOTE: If you submit your email address, it will be kept private (only Mozilla will be able to see that data). Personal information like IP and email addresses will not show up in public Talkback reports or query results. | ||
== | == As a developer for Mozilla's SVG code I'd like to learn how to narrow crash results to crashes occuring on SVG content. == | ||
There are a number of ways to narrow down your query results to find specific types of crashes. For this case we'll look at SVG, but the same approach can be taken for any part of the code, feature, or component. Using the QuickSearch query tool at [http://talkback-public.mozilla.org/talkback/fastfind.jsp http://talkback-public.mozilla.org/talkback/fastfind.jsp] | There are a number of ways to narrow down your query results to find specific types of crashes. For this case we'll look at SVG, but the same approach can be taken for any part of the code, feature, or component. Using the QuickSearch query tool at [http://talkback-public.mozilla.org/talkback/fastfind.jsp http://talkback-public.mozilla.org/talkback/fastfind.jsp] | ||
, you can try the following: | , you can try the following: | ||