-
-
Notifications
You must be signed in to change notification settings - Fork 200
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
MarkDownload downloads file with incorrect filename #39
Comments
I confirm the same behavior in the Edge browser. Specifically, when the original title of the page contains For example, when the title is "Coffee and Tea 24/7 restaurant", the resulting path will be
Where the filename will be |
@nikiluk, your issue appears to be #40, which I think I have now resolved. @MercuryOoO I'm pretty sure yours is a duplicate of #10 (but with more info, so I might close #10 as the duplicate). |
@deathau thank you! I've downloaded the repo to try the update.
|
@nikiluk yeah, I've got a bit of a WIP in there regarding an attempt to download images relative to the md file which is still buggy. You might have to go back a commit or two to find something stable |
@deathau Thanks for your advice. Although my issue is caused by “Nimbus Screenshot & Screen Video Recorder”, it is actually a deeper and more common issue. Exactly the same issue has been described clearly in the following places:
Since the issue has been marked as WontFix by upstream Google, you may close the issue. |
SingleFile addon can fix such bug by the following: I hope MarkDownload addon can have similar configuration. |
For those who found this issue and still having hashed filename, just go to Options > Download Mode > Choose Content Link. It will give you correct filename, at the cost of downloading images been disabled. |
Chrome: 87.0.4280.88 (64 bits)
MarkDownload: 2.4.1
OS: Windows 10 (10.0.19042)
Issue Ref: #10
This issue seems to be related to Chrome download API as it was occurred( Issue 1008884: chrome download API downloads file with incorrect filename ) I'm not sure which party should solves this issue first. The same issue appears in different Chrome plugins (such as Save Images Issue ref ). If this problem cannot be solved temporarily, I hope someone can provide some temporary solutions, thank you!
The text was updated successfully, but these errors were encountered: