You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.)
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:
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):
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.
The text was updated successfully, but these errors were encountered: