Closed
Bug 1234321
Opened 8 years ago
Closed 8 years ago
foreignInstall add-ons should never update to preliminary signed versions
Categories
(Firefox :: Extension Compatibility, defect)
Firefox
Extension Compatibility
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mconnor, Unassigned)
References
Details
Not sure if this is the right place for this, I flipped a coin. Please move as needed. If an add-on has been sideloaded, upgrading to a preliminary signed add-on version will result in a disabled add-on. We simply shouldn't update those users.
Comment 1•8 years ago
|
||
(In reply to Mike Connor [:mconnor] from comment #0) > Not sure if this is the right place for this, I flipped a coin. Please move > as needed. > > If an add-on has been sideloaded, upgrading to a preliminary signed add-on > version will result in a disabled add-on. We simply shouldn't update those > users. Can you clarify what a "preliminary signed add-on" is please? And why is it disabled?
Comment 2•8 years ago
|
||
(In reply to Andy McKay [:andym] from comment #1) > (In reply to Mike Connor [:mconnor] from comment #0) > > Not sure if this is the right place for this, I flipped a coin. Please move > > as needed. > > > > If an add-on has been sideloaded, upgrading to a preliminary signed add-on > > version will result in a disabled add-on. We simply shouldn't update those > > users. > > Can you clarify what a "preliminary signed add-on" is please? And why is it > disabled? He means a "preliminarily reviewed add-on", which has passed the AMO preliminary review, and got signed as a result, but has not undergone the comprehensive review. IIUC, sideloaded add-ons are disabled unless they have passed the comprehensive review; and as long as bug 1233459 isn't FIXED, the foreignInstall flag which marks an add-on as sideloaded cannot be cleared other than by uninstalling the add-on (updating isn't enough).
Comment 3•8 years ago
|
||
(In reply to Tony Mechelynck [:tonymec] from comment #2) > (In reply to Andy McKay [:andym] from comment #1) > > (In reply to Mike Connor [:mconnor] from comment #0) > > > Not sure if this is the right place for this, I flipped a coin. Please move > > > as needed. > > > > > > If an add-on has been sideloaded, upgrading to a preliminary signed add-on > > > version will result in a disabled add-on. We simply shouldn't update those > > > users. > > > > Can you clarify what a "preliminary signed add-on" is please? And why is it > > disabled? > > He means a "preliminarily reviewed add-on", which has passed the AMO > preliminary review, and got signed as a result, but has not undergone the > comprehensive review. IIUC, sideloaded add-ons are disabled unless they have > passed the comprehensive review; and as long as bug 1233459 isn't FIXED, the > foreignInstall flag which marks an add-on as sideloaded cannot be cleared > other than by uninstalling the add-on (updating isn't enough). Right, thanks, I should have got that.
Comment 4•8 years ago
|
||
If bug 1245956 happens, then this will be irrelevant.
Comment 5•8 years ago
|
||
Based on bug 1245956, this can be closed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•