Closed
Bug 483620
Opened 17 years ago
Closed 17 years ago
Feature request: Add user confirmation to override maxVersion limitation for extensions
Categories
(Firefox :: Extension Compatibility, enhancement)
Firefox
Extension Compatibility
Tracking
()
VERIFIED
INVALID
People
(Reporter: morten.larsen, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Often, when a new point release, especially a new beta, pre, etc. release comes out, extensions are automatically disabled, or new extensions can't be installed until they are upgraded to the latest point release of Firefox.
This forces to the user to choose between the latest release of the browser, or not being able to use extensions.
It would be very useful to have a UI way to let the user override the maxVersion setting in the extension.
Reproducible: Always
Steps to Reproduce:
1. Upgrade the browser to a recent build.
2. Notice how extensions are disabled automatically.
Actual Results:
Extensions are disabled with no possibility for the user to tell the browser to keep the extensions anyway.
Expected Results:
The extension installer should ask if the (seemingly) incompatible extensions should be installed anyway.
Comment 1•17 years ago
|
||
This already exists. http://kb.mozillazine.org/Extensions.checkCompatibility Asking a user if each of his extensions work is a bad idea. This is a hidden pref and no UI for it will be developed.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Comment 2•17 years ago
|
||
There is a reason why we have this check.
If we would make an easy UI for override we would not need the version check at all. And after that all user would complain about crashes, not working things...
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•