Support/Firefox Features/Clean up user profile: Difference between revisions

update status
No edit summary
(update status)
Line 69: Line 69:
** The safe mode dialog could provide a method to reset the profile
** The safe mode dialog could provide a method to reset the profile
* We need to make the distinction between the reset process and making changes in safe mode permanent more clear as they appear to do the same thing in the UI. In reality, resetting involves more data loss since it's actually going to migrate only high priority data to a new profile.
* We need to make the distinction between the reset process and making changes in safe mode permanent more clear as they appear to do the same thing in the UI. In reality, resetting involves more data loss since it's actually going to migrate only high priority data to a new profile.
* Use a file in the profile to keep track of crashes and whether the installer requested a repair
* Use prefs in the profile to keep track of crashes
** rs implies that the installer doesn't know about profiles so adding a command-line arguments and/or environment variable can be used
* Add command-line arguments and/or environment variables to launch the reset process
** The data in the file should be cleaned up:
*** When it applies to a previous version – already have code to do this for compatibility.ini
*** After a successful startup
**** Could use same event as session restore or something earlier?
** What about non-profile related crashes?
*** Is there any way we can detect this?
**** Ability to disable certain add-ons in safe mode may be enough
***** Can all add-ons be disabled?
* Migration to a new profile
* Migration to a new profile
** Do this in a way that extends to other applications
** Use profile migrator infrastructure
* Migration of Places data (notes from rnewman)
* Migration of Places data (notes from rnewman)
** Queries refer directly to a Places ID. If you do a low-level migration to a new DB, make sure that you don't break those foreign pseudo-keys!
** Queries refer directly to a Places ID. If you do a low-level migration to a new DB, make sure that you don't break those foreign pseudo-keys!
Line 88: Line 80:
** Note that Sync whitelists prefs to sync between devices (services.sync.prefs.*). You might want to think about that.
** Note that Sync whitelists prefs to sync between devices (services.sync.prefs.*). You might want to think about that.
** Similar caveats apply to other data stored in Sync. Making this feature work correctly with Sync will need a little bit of thought.
** Similar caveats apply to other data stored in Sync. Making this feature work correctly with Sync will need a little bit of thought.
|Feature implementation notes={{bug|294260}} - Safe Mode: Auto detect previous start-up failure and offer to start in safe mode
|Feature implementation notes=#{{In progress}} {{bug|294260}} - Safe Mode: Auto detect previous start-up failure and offer to start in safe mode
#{{In progress}} Code to create a new profile
# UI to reset profile
#* startup crashes
#* about:support
#{{In progress}} {{bug|273874}} - Create migrator with bookmark support and simple file copies
# Installer Reset option
# Other migrations
## passwords
## add-ons
## ...
# Privacy - Functionality to support removing the old profile
}}
}}
{{FeatureInfo
{{FeatureInfo
Line 99: Line 102:
}}
}}
{{FeatureTeamStatus
{{FeatureTeamStatus
|Feature engineering status=Researching implementation options
|Feature engineering status=Startup crash detection nearly complete.  Migrator + Bookmark Import for review soon
|Feature engineering notes=Plan is to stub migrators to just copy the relevant files initially and then iteratively improve them to better handle corrupt files.
|Feature security status=sec-review-needed
|Feature security status=sec-review-needed
|Feature qa status=In progress
|Feature qa status=In progress
|Feature qa notes=[http://mzl.la/vv96eq Test Plan]
|Feature qa notes=[http://mzl.la/vv96eq Test Plan]
}}
}}
Confirmed users
933

edits