Closed Bug 1585071 Opened 5 months ago Closed 5 months ago

Extension block request: IDM Integration Module

Categories

(Toolkit :: Blocklist Policy Requests, task)

task
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: TheOne, Assigned: TheOne)

Details

(Whiteboard: [extension])

Extension name IDM Integration Module
Extension versions affected 0 - 6.35.5
Platforms affected <all platforms>
Block severity hard

Reason

Some versions of this add-on violate Mozilla's add-on policies by using unreviewable source code. Please update to a newer version.

Extension GUIDs

mozilla_cc3@internetdownloadmanager.com

The block has been pushed.

Group: blocklist-requests
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED

Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]:
[Links (documentation, blog post, etc)]:

So all pc users got affected cause of an android user ?

(In reply to Andreas Wagner [:TheOne] [use NI] from comment #1)

The block has been pushed.

Like can you undo said block or atleast give us an option to enable once again cause you taking it away from us just seems rather dumb

This is really not useful, blocking some extension without giving the user choices what to do is counterproductive. I'm really thinking to switch my primary browser because of it. Too bad :(

Thank you everyone for the comments and inquiries you have made here, I understand this is an issue that brings up a lot of questions. At the same time, this is a bug tracker meant mostly for technical discussion around the actions taken. Note also we generally don't discuss the methodologies or details about the block.

Therefore, I am restricting comments to this bug. The path forward is to update the add-on to the latest version, which is not blocked.

If you have further questions, please post them to our discussion forums: https://discourse.mozilla.org/c/add-ons .

Thank you for your understanding.

Restrict Comments: true
You need to log in before you can comment on or make changes to this bug.