Jump to content

Incompatible with Chrono Download Manager extension


Cats869

Recommended Posts

Hello,

I am currently running Google Chrome Version 87.0.4280.141 and have Malwarebytes Browser Guard v2.2.17 and Chrono Download Manager v0.11.0 installed in my extensions.

Before, I did not have Chrono Download Manager installed and the Malwarebytes Browser Guard was working fine. After installing the Chrono Download Manager extension, Malwarebytes Browser Guard would display an error every time I downloaded a file. Not too sure why this keeps happening.  image.png.99e8ab314718f182bbfe6767117c1be4.png

I also get this error but not sure if it is 100% relatable but it seems to be another issue with compatibility.

image.png.9b48a4270876a9e59b48e4e733fc3cc0.png

 

image.png.ec1a938507e97be4d940d2ceafe10f42.png

 

 

Thanks in advance.

Link to post
  • Staff

There are known incompatibilities with any browser extension that renames files as they are being downloaded.  I would recommend turning off Browser Guard for the site where the issue you have described is occurring.

Link to post
  • 11 months later...

This has been a continuous issue for myself as well — irrespective of the site downloaded from (MBG 2.3.14 is currently installed in Brave and Slimjet, along with MWB Premium 4.5.0.152; this has not been an issue with Firefox ESR).

Is there a way to disable the download naming component in the MBG and defer to Chrono DM in the handling of d/l naming and end this annoying conflict?  (If not, then could that configuration feature be added in a future release?)

Thank you.

Link to post
  • Staff

No problem.  I just heard back from the developer.  Your download manager and Browser Guard are both trying to use the same browser API to assure that no "funny business" is happening when you are trying to download a file.  The API in use is the most appropriate one for this purpose.  Unfortunately, only one extension can have a listener attached to that API at any given time.  As an outsider, I don't think that trying to configure primary/secondary access to the API would be viable.  All vendors would want primary access, and we would be back where we started from.

  • Like 1
Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.