Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Conflict with another Chrome extension #187

Closed
MGuerrera opened this issue Aug 28, 2024 · 1 comment
Closed

[BUG] Conflict with another Chrome extension #187

MGuerrera opened this issue Aug 28, 2024 · 1 comment
Labels
browser-behavior bug Something isn't working chromium Chromium based browser

Comments

@MGuerrera
Copy link

MGuerrera commented Aug 28, 2024

Describe the bug
I report a conflict with the "Double-click Image Downloader" extension.
When the latter is installed and active, "Media Harvest" ignores the save location and filename pattern settings: all files are simply saved to the Downloads folder with an alphanumeric name and jpg_orig or png_orig extensions.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Chrome Store
  2. Install Double-click Image Downloader extension.
  3. Refresh the X page.
  4. Try to download a media content.

Expected behavior
The file should be downloaded with the chosen filename pattern, in the designated location, with the expected extension.

Desktop (please complete the following information):

  • OS: macOS Sonoma
  • Browser: Chrome
  • Chrome Version: 127.0.6533.120 (Official Build) (arm64)
  • "Double-click Image Downloader" Version: 71.2
  • "Media Harvest" Version: 4.2.8 (chrome)

Additional context
I've already looked at this thread, which identifies the problem and suggests turning off extensions that use a particular Chrome API.
Thanks to this suggestion I was able to identify the type of conflict and the extension that triggers it, but having needed it, I hope a solution can be found to make them coexist.

@MGuerrera MGuerrera added the bug Something isn't working label Aug 28, 2024
@MGuerrera MGuerrera changed the title [BUG] Conflict with other Chrome extension [BUG] Conflict with another Chrome extension Aug 28, 2024
@EltonChou EltonChou added chromium Chromium based browser browser-behavior labels Aug 29, 2024
@EltonChou
Copy link
Owner

Thanks for your well-formated report.

This a embarrassed issue for extension.
It is a bug for users, because the filename was modified.
But it is not a bug for this extension, because extension has passed correct filename to browser.
The root cause is chromium browser's behavior, the teams decide to do this.
I have tracked this chromium issue for few years.
Unless chromium team decides to change this behavior, it seems like there is no method to prevent this issue.

I will add a notification to let user know the filename might be overwritten by other extension in v5.0.0.

(You can try the Aggressive mode in options page. It may fix this issue, but it will cause some buggy behaviors to other extension or in some download situations.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser-behavior bug Something isn't working chromium Chromium based browser
Projects
None yet
Development

No branches or pull requests

2 participants