Features/Desktop/Firefox reset option on reinstall
Status
Firefox_reset_option_on_reinstall | |
Stage | Feature Inbox |
Status | In progress |
Release target | ` |
Health | OK |
Status note | Firefox approach ready to proceed. NSIS approach dependent on the stub installer and would require new mockups for it. |
Team
Product manager | Asa Dotzler |
Directly Responsible Individual | Michael Verdi |
Lead engineer | Robert Strong |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | ` |
UX lead | Madhava Enros |
Product marketing lead | ` |
Operations lead | ` |
Additional members | Matthew Noorenberghe |
Open issues/risks
Decide on one of the two approaches in stage 3.
Stage 1: Definition
1. Feature overview
The Firefox Reset is effective in fixing many issues involving the profile folder including removing unwanted add-ons and resetting the preferences that they have changed. Currently this feature is hidden in about:support and making it discoverable without a trip to the support site could help millions of Firefox users recover from issues that make Firefox unusable.
A bug has been filed for this work: https://bugzilla.mozilla.org/show_bug.cgi?id=750979
More info here: https://wiki.mozilla.org/Support/Firefox_Features/Clean_up_user_profile
2. Users & use cases
A user determines that "something" is wrong with Firefox, so they attempt to fix it by reinstalling. When Firefox (or the installer) detects that the same version of Firefox already exists on the computer it will offer the option to repair Firefox by resetting it to its default state.
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
There are two major approaches:
- Firefox itself detects the re-install. (Cross-platform and written in JS)
- Firefox can remember file modification times and the last version used to detect a re-install.
- The Windows installer detects the re-install. (Windows-only using NSIS)
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
`
Feature details
Priority | Unprioritized |
Rank | 999 |
Theme / Goal | ` |
Roadmap | ` |
Secondary roadmap | ` |
Feature list | ` |
Project | ` |
Engineering team | ` |
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | ` | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | ` | ` |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |