Closed
Bug 1024690
Opened 11 years ago
Closed 7 years ago
Regularly run a background health report check to identify and resolve issues
Categories
(Firefox Health Report Graveyard :: Client: Desktop, defect, P5)
Firefox Health Report Graveyard
Client: Desktop
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
Firefox 34
People
(Reporter: benjamin, Unassigned)
References
Details
(Keywords: meta, Whiteboard: [measurement:client])
We want FHR to be more proactive in helping users who are experiencing problems. Bug 1024687 will have a UI spec, but under the hood what we're going to want to do is run the server FHR component in a hidden context. If we need to prompt the user about specific issues, we can use the support API to do that; otherwise it can just close itself.
Some unresolved issues here about how we do this without affecting startup performance; whether we do this on *every* startup or just daily; also we'll probably want to separate out the "display" portions of the server-side code from the problem-calculation bits so that we don't bloat downloads unnecessarily.
Comment 1•11 years ago
|
||
Morphing this into a top-level bug, making this the top of the chain for tracking this project.
Updated•11 years ago
|
Summary: Regularly (on startup?) run a hidden healthreport check to check for and solve issues → Regularly run a background health report check to identify and resolve issues
Comment 2•11 years ago
|
||
I'm tech lead for this bug tree.
Comment 3•11 years ago
|
||
Not working on this after switching teams.
Assignee: gps → nobody
Status: ASSIGNED → NEW
Updated•10 years ago
|
Priority: -- → P5
Whiteboard: [measurement:client]
Comment 4•7 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=1497137; component has been deprecated.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•7 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
•