Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Removed add-ons's data still in about:config

  • 3 odpowiedzi
  • 1 osoba ma ten problem
  • 14 wyświetleń
  • Ostatnia odpowiedź od SannNord

more options

I have found several instances where Firefox add-ons that have been removed (in some cases after several release upgrades) still have the add-on setting information contained in about:config!?!

For example, the support for the NoSquint add-on has stopped. Two upgrades later I still have NoSquint entries in about:config! It seems to me that these 'artifacts' should be deleted from about:config when the add-on itself is deleted. How can I remove these about:config entries?

I have found several instances where Firefox add-ons that have been removed (in some cases after several release upgrades) still have the add-on setting information contained in about:config!?! For example, the support for the NoSquint add-on has stopped. Two upgrades later I still have NoSquint entries in about:config! It seems to me that these 'artifacts' should be deleted from about:config when the add-on itself is deleted. How can I remove these about:config entries?

Wybrane rozwiązanie

You can reset prefs leftover by extensions on the about:config page via the right-click context menu to the default value to have them removed on the next start.

Alternatively you can delete possible user.js and numbered prefs-##.js files and rename/remove the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in current Firefox releases.

You can use this button to go to the current Firefox profile folder:

Przeczytaj tę odpowiedź w całym kontekście 👍 0

Wszystkie odpowiedzi (3)

more options

Yep, extensions don't uninstall completely, preferences are left behind. There's no requirement that an extension remove those preferences when removed.

Best way to get rid of those unneeded preferences in about:config is to create a new Profile.

Overall, with the extension gone those old prefs are useless, the code that 'hooks' prefs is Firefox is gone and other than being clutter those prefs aren't going to affect Firefox negatively.

more options

Wybrane rozwiązanie

You can reset prefs leftover by extensions on the about:config page via the right-click context menu to the default value to have them removed on the next start.

Alternatively you can delete possible user.js and numbered prefs-##.js files and rename/remove the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in current Firefox releases.

You can use this button to go to the current Firefox profile folder:

more options

Two reasons behind my original post:

  • to minimize the uniqueness of my Firefox browser 'fingerprint' (check out https://panopticlick.eff.org)
  • eliminating CRUFT is always a good thingbecause esidual artifacts are never helpful

Thanks for the feedback!