Similar to what we've done a few years ago (Bug 1620621), we'd like to (re-)introduce a new soft blocking mechanism that is backed by a bloom filter, etc. This bug tracks the backend work to do so.
Bug 1917845 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Similar to what we've done a few years ago (Bug 1620621), we'd like to (re-)introduce a new soft blocking mechanism that is backed by a bloom filter, etc. This bug tracks the backend work to do so. Here is a list of things we need to pay attention to (from the PRD): - When an add-on version is soft-blocked by Mozilla, it should be disabled in both the Firefox desktop and mobile versions - Provide the ability for a user to re-enable the soft-blocked version in about:addons - Prevent new installation of soft-blocked versions with an error explaining why it cannot be installed - Allow the user to disable or re-enable blocking capabilities in Firefox - A soft-blocked add–on version should automatically update to a newer, approved and not blocked, add-on version if the user has auto-updates enabled - If an add-on somehow ends up in both the soft-block and hard-block lists, the hard-block should take precedent