Features/Firefox/PluginCrashComments: Difference between revisions

Revision as of 17:10, 9 May 2011

Once you have created your Feature page, please remove this paragraph and link to your page from the Features Inbox, where a team will triage it and move it into the appropriate Feature list. If you have any questions, please contact Deb.

Feature	Status	ETA	Owner
PluginCrashComments	One or two sentence status report.	Not scheduled yet	Sheila Mooney

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 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.

Another side benefit of getting this implemented is Electrolysis. We will want to enable users to submit comments when the content process crashes.

Team

Feature Manager: Sheila Mooney
Lead Developer:
Product Manager:
QA:
UX: Jennifer Boriss
Accessibility:
Security:
Privacy:

Release Requirements

Next Steps & Open Issues

Related Bugs & Dependencies

We are currently tracking this feature in Bug 648675.

Risks

Use Cases

Designs

Design details and mockups can be found in Bug 648675.

Test Plans

Goals

Non-Goals

Other Stuff

Legend (remove if you like)

	Healthy: feature is progressing as expected.
	Blocked: feature is currently blocked.
	At Risk: feature is at risk of missing its targeted release.
ETA	Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.

Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.

@@ Line 19: / Line 19: @@
 == 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.