Closed Bug 1549991 Opened 1 year ago Closed 1 year ago

Do not include a remove action for an abuse report on an add-on that doesn't have PERM_CAN_UNINSTALL

Categories

(Toolkit :: Add-ons Manager, defect, P1)

68 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: rpl, Assigned: rpl)

References

Details

Attachments

(1 file)

I'm not yet 100% convinced that we shouldn't hide the report action for add-ons that are system add-ons (or built-in add-ons/themes), but during Bug 1543377's review rounds we discussed about it with mstriemer and we agreed to show the report action for any extension or theme visible in about:addons, in other words "currently we don't assume that the user shouldn't be able to submit report on an add-on bundled in a build or developed by Mozilla itself" (at least until we re-evaluate this and decide that there are specific reasons to do otherwise).

In the meantime, at least, we shouldn't offer a remove action for a report submitted for an add-on that doesn't have a PERM_CAN_UNINSTALL permission flag.

Assignee: nobody → lgreco
Blocks: 1543377
Status: NEW → ASSIGNED
Priority: -- → P1
Pushed by luca.greco@alcacoop.it:
https://hg.mozilla.org/integration/autoland/rev/c24c083425d0
No remove action on report submitted for add-ons without PERM_CAN_UNINSTALL. r=flod,mstriemer
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Regressions: 1561411
You need to log in before you can comment on or make changes to this bug.