> changed preferences, hsts data, intermediate certificate DB contents that > This means you actually lose a lot of stuff, not just add-ons but also any > 4) make the new clean-ish profile the default (or at least give it the same > 2) copy some specific data back into the clean profile from the old profile > The "profile repair utility" of record is "firefox refresh". Without knowing anything about indexedDB, I'm pretty sure it would be easier to write a system add-on that just wiped the indexeddb database if it was corrupt/unreadable. That seems like a really big hammer to fix whatever issues we expect people to have with a downgrade (which I assume is basically the indexeddb issue? Are there other issues we're aware of?).
etc., by doing the reset, which also seems undesirable. It's not straightforward, I think, certainly not if we want to disable all of them, but even without that keeping add-on state as well as add-on files isn't trivial, AIUI.īut then, even if we did that we'd then wipe all the about:preferences and about:config settings, toolbar customizations, etc. This means you actually lose a lot of stuff, not just add-ons but also any changed preferences, hsts data, intermediate certificate DB contents that have been built up over time (and/or custom certs you installed), etc. What that actually does is:Ģ) copy some specific data back into the clean profile from the old profileĤ) make the new clean-ish profile the default (or at least give it the same name as the old profile) The "profile repair utility" of record is "firefox refresh". > A system add-on allows enabling that functionality as early as Firefox 56. > add-ons that are not supported on 57 anymore) > that users downgrading do it because they want to have access to their > does but does not remove the plugins or addons that are installed (we assume 3 The profile repair utility does what the current profile repair utility
0 kommentar(er)
