为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Retrying Save As Web Page, Complete does not retry all files

  • 3 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 Jidis Safi

more options

Using 118.0.1 (64-bit) under Linux Mint 21.2.

Apparent bug: Retrying failed "Web Page, Complete" case of "Save Page As..." does not retry downloading files.

  1. Observed behavior:

1. With the extension "DuckDuckGo Privacy Essentials" enabled, typically if I do "Save Page As..." and choose "Web Page, Complete", then one or more files in the resulting "... Files" folder is missing compared to if the extension is disabled. This is probably as it should be. But...

2. In the downloads dropdown the download is shown as "failed". This is arguably as it should be, though the lack of information as to exactly which file download failed is unhelpful. Or arguably it is not as it should be, since from the point of the privacy extension user the download did not fail, it succeeded completely. But...

3. ***If I then click on the retry icon, it re-downloads *only the HTML*, not the files folder, and reports success.***

  1. Expected behavior:

If a "Save As..." "Web Page, Complete" fails, then retry should attempt to re-download all the files, or at least all the ones thought to have failed.

Using 118.0.1 (64-bit) under Linux Mint 21.2. Apparent bug: Retrying failed "Web Page, Complete" case of "Save Page As..." does not retry downloading files. # Observed behavior: 1. With the extension "DuckDuckGo Privacy Essentials" enabled, typically if I do "Save Page As..." and choose "Web Page, Complete", then one or more files in the resulting "... Files" folder is missing compared to if the extension is disabled. This is probably as it should be. But... 2. In the downloads dropdown the download is shown as "failed". This is arguably as it should be, though the lack of information as to exactly which file download failed is unhelpful. Or arguably it is not as it should be, since from the point of the privacy extension user the download did not fail, it succeeded completely. But... 3. ***If I then click on the retry icon, it re-downloads *only the HTML*, not the files folder, and reports success.*** # Expected behavior: If a "Save As..." "Web Page, Complete" fails, then retry should attempt to re-download all the files, or at least all the ones thought to have failed.

被采纳的解决方案

Yes I did. Why is this link not on the Firefox support page? I looked for it but could find nothing but a link to this community.

定位到答案原位置 👍 0

所有回复 (3)

more options
more options

选择的解决方案

Yes I did. Why is this link not on the Firefox support page? I looked for it but could find nothing but a link to this community.

more options

This looks like the most recent, non-archived report on the same issue I've had for ages, and I'm actually on Windows 7 64-bit (currently using Firefox ESR Version 115.2.0). If it helps any, I checked a few things just now after reading suggestions in some of the other posts on it.

- Path length seems to have no connection. I stripped the saved .html file/folder name down to a single word, saved in the root of my storage drive, and it still allegedly fails.

- On the couple checks I just did, the actual batch of files in the saved "_files" folder of the failed save checksums OK against those of a successful save after using the retry button. I thought that in the past, it was saving an incomplete batch of files, where most of the images weren't saved, but I guess that's not always the case.

- The actual .html file, on the other hand, did not match on checksums, so maybe the failure is in that file rather than the corresponding folder, unless the file content normally changes due to dynamic ads or something else.

It's not 100% consistent, as some "web page, complete" saves go through with no problem. It also might be worth noting that I seem to be one of the few who run with Windows *not* set to hide all the file extensions. I think that's caused some related issues in the past that none of the people running on the default seemed to have.

Maybe something in there could help narrow it down. - Thanks!