Confirmed users
2,492
edits
Features/Firefox/PluginCrashComments: Difference between revisions
Jump to navigation
Jump to search
→Summary
No edit summary |
|||
| Line 19: | Line 19: | ||
== Summary == | == Summary == | ||
Today, if a plugin crashes, the user is prompted to submit a crash report. However, they are not provided with an interface for entering a comment alongside the crash report as they can with other types of crashes. Although comments are optional and we rely on the users ability to give us informed information about what they are doing at the time of the crash, they are another piece of data that can assist us in diagnosing a problem. Plugin crashes are particularly difficult to analyze. | Today, if a plugin crashes, the user is prompted to submit a crash report. However, they are not provided with an interface for entering a comment alongside the crash report as they can with other types of crashes. Although comments are optional and we rely on the users ability to give us informed information about what they are doing at the time of the crash, they are another piece of data that can assist us in diagnosing a problem. Plugin crashes are particularly difficult to analyze so any additional data is helpful. | ||
A recent security study showed a pretty high percentage of users liked the idea of providing comments and crash reports to help improve Firefox. In more than one case during the course of Firefox 4 development, reading the users' comments has lead to the resolution of a serious top crash in the product. For this reason we think this is a pretty important enhancement to get in. | A recent security study showed a pretty high percentage of users liked the idea of providing comments and crash reports to help improve Firefox. In more than one case during the course of Firefox 4 development, reading the users' comments has lead to the resolution of a serious top crash in the product. For this reason we think this is a pretty important enhancement to get in. | ||