Closed Bug 801932 Opened 13 years ago Closed 13 years ago

[Settings] Expose preference to always/never send crash reports (default is to ask every time)

Categories

(Firefox OS Graveyard :: Gaia, defect, P1)

defect

Tracking

(blocking-basecamp:+)

RESOLVED DUPLICATE of bug 801931
blocking-basecamp +

People

(Reporter: lco, Assigned: Margaret)

References

()

Details

See pg. 8 of the spec: http://people.mozilla.com/~lco/Crash_Reporting_B2G/ The user has the ability to toggle between: 1. Always send a report 2. Never send a report 3. Ask me each time a crash occurs. The user can also find a link to learning more about what a crash report contains and a page for displaying Crash Data (About: Crashes)
The b2g code is already using the "app.reportCrashes" boolean pref for this: http://mxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.js#90 The code in there will be changing when we implement bug 801809, so we could replace this with a tri-state pref to represent always/never/ask. Or we remove the pref from b2g.js, and then use the non-set case for "Ask me each time", true for "Always send", and false for "Never send". The settings UI that needs to be made for this bug shouldn't depend on the new crash UI, so I don't think anything blocks progress on this bug if someone wants to work on it.
Simplifying bug summary. My current patch for bug 801809 uses "app.reportCrashes", where true/false correspond to always/never send, and if the preference isn't set we'll ask each time.
Summary: [Settings] As a user, I want to set a general preference for whether or not to send a crash report to Mozilla so that I can minimize interruptions from the OS when a crash occurs. → [Settings] Expose preference to always/never send crash reports (default is to ask every time)
(In reply to Margaret Leibovic [:margaret] from comment #2) > My current patch for bug 801809 uses "app.reportCrashes", where true/false > correspond to always/never send, and if the preference isn't set we'll ask > each time. We're going to change this. Follow along in bug 801809 for details!
Feature work for v1 and sounds like Margaret may pick this up.
blocking-basecamp: --- → +
Priority: -- → P1
Depends on: 801931
(In reply to Chris Lee [:clee] from comment #4) > Feature work for v1 and sounds like Margaret may pick this up. Yeah, I'll take this.
Assignee: nobody → margaret.leibovic
This is going to be fixed in bug 801931. Can we move the blocking flag over there?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.