Firefox page saving: Redownload instead of saving from RAM.
Hello. I noticed that Firefox does actually save pages by re-downloading them like Google Chrome. Older versions of Firefox actually saved them directly from RAM, but recently, Firefox re-downloads pages too, which is a terrible realisation I made today. I saved so many pages, and now I know, that all my saved pages are crippled.
Wšě wotmołwy (7)
I must say I feel a bit betrayed now.
I don't really understand the problem going on. Firefox has a cache of pages you've visited, like all browsers, but it's stored in your hard drive, not RAM
Note that you are behind on updates, Firefox 61.0.2 is current.
- Help -> About Firefox
- https://support.mozilla.org/en-US/kb/update-firefox-latest-version
If you want an exact copy then maybe use a full screen screenshot.
fsckFox said
I saved so many pages, and now I know, that all my saved pages are crippled.
What do you mean by this? Is there a problem when you open one of those pages?
There are sites that build the page dynamically at load time, and the source code is just a shell. If you save using "Web page, HTML only" then that is pretty useless. However, when you save using the "Web page, complete" format (the one that creates a companion folder of files), Firefox saves the rendered version of the page as you see it rather than the original shell. (I've even noticed modifications inserted by add-ons in that code.)
Unfortunately, some pages contain scripts that force authentication or redirect to the server when you open a saved page. This is difficult to work around unless you disable JavaScript, which could cause other issues with the page.
If you don't need to edit the code or use the page interactively, PDF format or a full page screenshot may be more reliable formats than "live" HTML.
cor-el said
Note that you are behind on updates, Firefox 61.0.2 is current.
- Help -> About Firefox
- https://support.mozilla.org/en-US/kb/update-firefox-latest-version
If you want an exact copy then maybe use a full screen screenshot.
Does the new version fix this issue?
jscher2000 said
fsckFox saidI saved so many pages, and now I know, that all my saved pages are crippled.What do you mean by this? Is there a problem when you open one of those pages?
There are sites that build the page dynamically at load time, and the source code is just a shell. If you save using "Web page, HTML only" then that is pretty useless. However, when you save using the "Web page, complete" format (the one that creates a companion folder of files), Firefox saves the rendered version of the page as you see it rather than the original shell. (I've even noticed modifications inserted by add-ons in that code.)
Unfortunately, some pages contain scripts that force authentication or redirect to the server when you open a saved page. This is difficult to work around unless you disable JavaScript, which could cause other issues with the page.
If you don't need to edit the code or use the page interactively, PDF format or a full page screenshot may be more reliable formats than "live" HTML.
Hello, jscher2000. ♦ Thank you really, really much. ♦
I am so happy, that you found the solution to my problem. Just two more questions.
- I am curious, why "HTML only" is enabled by default.
- You are apparently highly knowledgeable. How did you know about this?
fsckFox said
- I am curious, why "HTML only" is enabled by default.
- You are apparently highly knowledgeable. How did you know about this?
I think "Web page, complete" is the default in new installations or new profiles. If you reset the following preference, Firefox uses that option:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.
(2) In the search box above the list, type or paste save and pause while the list is filtered
(3) If you have a browser.download.save_converter_index preference, right-click it and choose Reset
This preference is updated after each Save; 0 (zero) corresponds to "complete"
Preferences can be modified by files Firefox reads at startup, such as user.js or by legacy extensions (in Firefox 56 and earlier). The following article has more information about the optional user.js file: How to fix preferences that won't save.
And how did I learn about this? Probably from bitter personal experience and by investigating odd behaviors to answer questions here.