New issue
Advanced search Search tips

Issue 843344 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Clean up old ExtensionPref entries

Project Member Reported by rdevlin....@chromium.org, May 15 2018

Issue description

ExtensionPrefs stores preferences related to extensions.  Many times, these are related to a specific extension, and each extension has an entry in the preference file, e.g.

"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa": {
  "pref1": <value>,
  "pref2": <value>
}

If a preference is made obsolete (e.g., pref1 is removed from the codebase), there is currently no easy way to remove this preference.  The typical approach of using MigrateObsoleteProfilePrefs() will not work because there is not a single, defined key for the pref entry (i.e., it will be extensions.settings.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.pref1).

We should add a method to ExtensionPrefs that cleans these up appropriately.

One such preference is the "has_set_script_all_urls" key.
 

Sign in to add a comment