Define a property for an extension's recommended status
Categories
(Toolkit :: Add-ons Manager, enhancement, P2)
Tracking
()
People
(Reporter: ddurst, Assigned: robwu)
References
(Blocks 1 open bug)
Details
(Whiteboard: [feature-scope])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
If we're going to show which extensions are recommended in about:addons, we need to be able to tell which ones are recommended.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
This bug is for defining a property on the AddonWrapper
. Something like:
let addon = await AddonManager.getAddonByID("recommended@addon");
addon.recommended === true;
Comment 2•5 years ago
|
||
Hi, I'd like to take this up if no one else is working on this. Can you give me any more details that'd help me while working on this? Thanks.
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Rithvik Patibandla[:rithvikp] from comment #2)
Hi, I'd like to take this up if no one else is working on this. Can you give me any more details that'd help me while working on this? Thanks.
Hi, Rithvikp, in setting a mentor I didn't mean to imply this is a good bug for a contributor -- I just wanted to note who the best person was to help someone new to this part of the code. However, this should probably be done internally. Sorry for causing confusion!
Comment 4•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Pushed by mstriemer@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0b8409408524 Define an isRecommended property for add-ons r=aswan
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Comment on attachment 9071510 [details]
Bug 1540253 - Define an isRecommended property for add-ons
Beta/Release Uplift Approval Request
- User impact if declined: Recommended add-ons installed from AMO will not be shown as recommended in Firefox.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1539699, Bug 1559112, Bug 1559131
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): On Nightly for a few days, warning and test failure fixed, has test coverage.
- String changes made/needed:
Assignee | ||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Comment on attachment 9071510 [details]
Bug 1540253 - Define an isRecommended property for add-ons
approved for 68.0b11
Comment 10•5 years ago
|
||
bugherder uplift |
Comment 11•5 years ago
|
||
Hello,
As per Comment 8, the “Needs manual testing from QE?” field is set to ‘NO’, however the “qe-verify -” flag is not set for this bug.
As per the above, will this fix require manual validation? If yes, could you please provide steps to reproduce in order to correctly test it and set the "qe-verify+" flag. Thanks!
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•