318338 - Implement central blacklisting of extensions

Status: RESOLVED FIXED

(Toolkit :: Add-ons Manager, defect)

Description

[Mike Connor [:mconnor]]

Tracking, see deps

Comment 1

[Robert Strong (they/them - no direct email)]

bug 250854 is for blacklisting via xpinstall and the permissions manager on the client and this bug is for centralized blacklisting of extensions. There is no dependency for bug 250854 to be fixed to fix this bug.

Comment 2

[Robert Strong (they/them - no direct email)]

I'd like to land the patch in bug 317406 when this lands since it also occurs when an item is not installed due to it being blacklisted.

Comment 3

[Robert Strong (they/them - no direct email)]

Attachment: UI Screenshots

Mike, attached is a screenshot of the EM with blacklisted items, notification dialog, and install denied dialog per the wiki and our discussions for your review.

Comment 4

[Robert Strong (they/them - no direct email)]

Attachment: really close

I just need to work a bit on getIncompatibleItems for this to be complete

Comment 5

[Robert Strong (they/them - no direct email)]

Resetting target milestone since the AMO work still needs to be completed in bug 290759

Comment 6

[Robert Strong (they/them - no direct email)]

Client side is done - remaining work to be done on AMO and www.mozilla.org. Changing milestone to beta 1 since the remaining work doesn't need to be / won't be finished by alpa 2

Comment 7

[Mike Connor [:mconnor]]

pushing out non-critical-path bugs to b2

Comment 8

[Robert Strong (they/them - no direct email)]

The remaining items are:
1) Add the ability to create the blocklist on AMO.
2) Create the blocklist page on http://www.mozilla.com/blocklist/

Comment 9

[Mike Connor [:mconnor]]

Client side pieces are in place, so resolving this, bug 290759 is the server side piece that remains,  which is now on the Fx2 blocker list.