Incompatible with Chrono Download Manager extension

[Cats869]

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.  

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

 

 

 

Thanks in advance.

[gonzo]

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.

[Cats869]

So it seems to happen on any website I am on. I guess it's more of a global issue since any file that is downloaded through that browser, the error would pop up for Malwarebytes. Now, there seems to be no side effect so I guess that's okay but still an issue nonetheless.

[AJNorth]

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.

[gonzo]

I have reached out to the developer to find out about future plans surrounding this topic. I will respond after I get a response and discuss it (if necessary).

[AJNorth]

Thank you, gonzo! 

(Apology for the double communication; was not not clear on how to communicate with you regarding your reply to an older post.)

All the best,

AJN

[gonzo]

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.

[AJNorth]

Perhaps I shall contact the Chrono Download Manager dev to see whether an accommodation can be made for competing extensions such as MBG.  Thank you for your efforts! 

Take good care.

Cheers,

AJN

[gonzo]

If you come up with anything that sounds good, please let us know.  Its a real issue that needs a better solution.