Closed
Bug 860238
Opened 12 years ago
Closed 10 years ago
Breakdown: Handle "Profile Reset" gracefully in FHR
Categories
(Firefox Health Report Graveyard :: Client: Desktop, defect)
Firefox Health Report Graveyard
Client: Desktop
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: adw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxgrowth])
I'm not sure what the current situation is with regard to the Profile Reset feature in Firefox, but we should ensure that at minimum we flag that a reset has occurred.
Updated•12 years ago
|
Comment 1•12 years ago
|
||
The ideal in my opinion:
* Profile Reset should append to times.json recording that a reset has occurred.
* Profile Reset also needs to preserve FHR preferences and state files.
* FHR (on desktop and mobile) should include profile reset events alongside profile creation time in the submitted report.
* Presumably PR involves closing and reopening firefox(.exe), so on desktop there's no need to notify any listeners; the next time FHR runs it'll spot changed add-ons at so forth.
* On Android, FHR is a separate chunk of Java, so further consideration is needed if and when Profile Reset makes it to Fennec.
Updated•11 years ago
|
Flags: needinfo?(sguha)
Updated•11 years ago
|
Blocks: fxdesktoptriage
Updated•11 years ago
|
Whiteboard: p=0
Updated•11 years ago
|
Flags: firefox-backlog+
Updated•11 years ago
|
No longer blocks: fxdesktopbacklog
Summary: Handle "Profile Reset" gracefully in FHR → Breakdown: Handle "Profile Reset" gracefully in FHR
Whiteboard: p=0 → p=3 [qa?]
Updated•10 years ago
|
Flags: needinfo?(sguha)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → adw
Status: NEW → ASSIGNED
Iteration: --- → 35.1
Points: --- → 3
Whiteboard: p=3 [qa?]
Updated•10 years ago
|
Flags: qe-verify-
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Whiteboard: [fxgrowth]
Updated•6 years ago
|
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•