[about:addons] Show legacy/unsigned extensions somewhere in HTML views
Categories
(Toolkit :: Add-ons Manager, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox67 | --- | disabled |
firefox68 | --- | wontfix |
firefox69 | --- | fix-optional |
People
(Reporter: mstriemer, Unassigned)
References
Details
(Whiteboard: [feature-scope])
We likely shouldn't kill the legacy/unsigned view since then there will be add-ons that the user has installed but can't see. These extensions should be shown somewhere, perhaps underneath the Disabled section in the regular extension listing. Including a message that the user may as well just uninstall these things already might not be a bad idea.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
These extensions should stay in their own tab. The message bar can likely go away, but we should confirm with product.
Amy, are we okay with removing the message on the extensions tab about legacy extensions? If users still have legacy extensions this message bar doesn't seem to be convincing them to remove the extensions. I've added this to the agenda for the Thursday meeting.
Comment 2•5 years ago
|
||
Since the legacy tab still appears for people who have legacy extensions installed, we can remove the message banner.
Reporter | ||
Comment 3•5 years ago
|
||
We just discussed this and these legacy extensions can't be run or parsed anymore. Instead of implementing the legacy view it looks like it would make more sense to show experiments (what the legacy pref controls now) in the regular list.
Comment 4•5 years ago
|
||
Do you need UX for this?
Comment 5•5 years ago
|
||
This is probably covered by 1544950, but that requires some new strings? Also, I'm taking this out of P1 because showing legacy as disabled (when they're disabled) is not wrong.
Updated•5 years ago
|
Reporter | ||
Comment 6•5 years ago
|
||
Legacy extensions are in the disabled list, we're planning on cleaning them out of the database and no further work will be done here.
Description
•