Closed
Bug 1318270
Opened 9 years ago
Closed 1 year ago
Should be made obvious that 'Remove all reports' removes both pending/unsubmitted and submitted reports
Categories
(Toolkit :: Crash Reporting, enhancement)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
FIXED
People
(Reporter: aryx, Unassigned)
References
Details
On about:crashes, the button 'Remove all reports' is next to the header 'Unsubmitted crash reports'. This can trick users into believing that it will only remove all pending crash reports. It should be made obvious that they will also use the information what crash reports they submitted.
Comment 1•9 years ago
|
||
Yeah I have always found that a bit annoying too... it's always been the case, just more obvious now that bug 512479 is in place.
Comment 2•8 years ago
|
||
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #0)
> On about:crashes, the button 'Remove all reports' is next to the header
> 'Unsubmitted crash reports'. This can trick users into believing that it
> will only remove all pending crash reports. It should be made obvious that
> they will also use the information what crash reports they submitted.
I have experienced this. I thought that it only removed pending crash reports and I clicked on it. Then all of my pending and submitted crash reports were deleted and I couldn't find any way to get them back. There appears to be no "Undo" or "Undelete" option.
Instead of permanently deleting the bug reports (considering they are only 1KB per report) they could be moved to another folder to be used as a recycle bin.
Something like:
%appdata%\Roaming\Mozilla\Firefox\Crash Reports\recycled
or
%appdata%\Roaming\Mozilla\Firefox\Crash Reports\hidden
or
%appdata%\Roaming\Mozilla\Firefox\Crash Reports\deleted
or
%appdata%\Roaming\Mozilla\Firefox\Crash Reports\archived
Updated•3 years ago
|
Severity: normal → S3
Comment 3•1 year ago
|
||
This was fixed in bug 1476062.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•