If the app disables extensions as being incompatible after an app upgrade, they can be re-enabled without warning in the EM. We should prevent this or give a very clear warning that doing so is ill advised.
If we're going to need new strings, we'll want to get this ASAP. Setting to blocking to get on Ben's radar.
I agree that there should be a warning. But I disagree that it should be disallowed. After changing to the Sept 3rd nightly all but 2 of my extensions were disabled. After manually enabling the other 8 or so, all worked flawlessly.
YES for warning. NO for disabling the re-enabling.
Seconded. Maybe a message like this might do the trick: "There is a good chance that this extension was disabled automatically because of compatibility reasons. Re-enabling the extension can cause problems or might not work at all, because the extension was NOT tested with this version of Firefox. Are you sure that you want to try to re-enable the extension anyway? [No] [Yes]" Or something like that.
Created attachment 157976 [details] [diff] [review] patch Prevent extensions disabled because of incompatibilities from being re-enabled, and show some visual feedback in the EM.
14 years ago
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
I've verified this in the windows branch build from 09/06
Can you explain the rationale behind the choice to completely disallow re-enabling "incompatible" extensions? Why would a simple warning, perhaps mentioning how to start Firefox in Safe Mode, be insufficent?
You need to log in before you can comment on or make changes to this bug.