MozillaWiki

Features/Firefox/PluginCrashComments: Difference between revisions

Page Discussion

Features/Firefox/PluginCrashComments (view source)

Revision as of 18:37, 30 August 2011

1,248 bytes removed ,  30 August 2011
no edit summary
No edit summary
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Once you have created your Feature page, please remove this paragraph and link to your page from the [[Features/Inbox|Features Inbox]], where a team will triage it and move it into the appropriate [[Features|Feature list]].  If you have any questions, please contact [[User:Dria|Deb]].
{{FeatureStatus
 
|Feature name=Plugin crash comments
{| class="fullwidth-table"
|Feature stage=Planning
|-
|Feature health=OK
| style="font-weight: bold; background: #DDD;" | Feature
}}
| style="font-weight: bold; background: #DDD;" | Status
{{FeatureTeam
| style="font-weight: bold; background: #DDD;" | ETA
|Feature product manager=Asa Dotzler
| style="font-weight: bold; background: #DDD;" | Owner
|Feature feature manager=Sheila Mooney
|-
|Feature qa lead=Vlad Ghetiu (irc: vladg)
<section begin="status" />
|Feature ux lead=Jennifer Boriss
| [[PluginCrashComments]]
}}
| {{StatusHealthy|status=One or two sentence status report.}}
{{FeaturePageBody
| Not scheduled yet
|Feature open issues and risks=Need to get this feature prioritized and an owner for the implementation.
| Sheila Mooney
|Feature overview=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.
<section end="status" />
|-
|}
 
== 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.
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.
Another side benefit of getting this implemented is Electrolysis. We will want to enable users to submit comments when the content process crashes.
 
|Feature ux design=Design details and mockups can be found in [https://bugzilla.mozilla.org/show_bug.cgi?id=648675 Bug 648675].
== Team ==
|Feature implementation notes=We are currently tracking this feature in [https://bugzilla.mozilla.org/show_bug.cgi?id=648675 Bug 648675].
 
}}
* '''Feature Manager''': Sheila Mooney
{{FeatureInfo
* '''Lead Developer''':
|Feature priority=P2
* '''Product Manager''':
|Feature roadmap=Plugin Interactions
* '''QA''':
|Feature list=Desktop
* '''UX''': Jennifer Boriss
|Feature engineering team=Desktop front-end
* '''Accessibility''':
}}
* '''Security''':
{{FeatureTeamStatus}}
* '''Privacy''':
 
== Release Requirements ==
 
== Next Steps & Open Issues ==
 
 
== Related Bugs & Dependencies ==
 
We are currently tracking this feature in [https://bugzilla.mozilla.org/show_bug.cgi?id=648675 Bug 648675].
 
== Risks ==
 
== Use Cases ==
 
== Designs ==
 
Design details and mockups can be found in [https://bugzilla.mozilla.org/show_bug.cgi?id=648675 Bug 648675].
 
== Test Plans ==
 
 
== Goals ==
 
 
== Non-Goals ==
 
 
== Other Stuff ==
 
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| 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.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Platform]]
[[Category:Services]]
[[Category:Mobile]]
[[Category:Other]]
Clee
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/306466...344823"