Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.
Solved Arhivirano

How to get old behaviour for firefox snapshot save back?

Firefox Troubleshooting
user801695 replied prije 13 godina
user801695
user801695

A couple versions ago (probably 3.6, since that is the last version that really worked problem free for me--so much for upgrades being better), I could save a website, and have it saved as I saw it: Unnecessary javascript was deleted and replaced by the text "script removed by snapshot save", sidebars and headers I blocked were not saved, and stylesheet changes via stylish/greasemonkey/etc. were taken into consideration.

  • I want that behaviour back.* How do I do it? Can anyone *please* help with this aggravating issue???
A couple versions ago (probably 3.6, since that is the last version that really worked problem free for me--so much for upgrades being better), I could save a website, and have it saved as I saw it: Unnecessary javascript was deleted and replaced by the text "script removed by snapshot save", sidebars and headers I blocked were not saved, and stylesheet changes via stylish/greasemonkey/etc. were taken into consideration. *I want that behaviour back.* How do I do it? Can anyone *please* help with this aggravating issue???

All Replies (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 saradnika

Odabrano rješenje

When I search for that message ("script removed by snapshot save") I find references to the "faithful snapshot" feature of the following add-on. Can you check whether this is what you are missing?

Mozilla Archive Format, with MHT and Faithful Save :: Add-ons for Firefox

user801695
user801695 Vlasnik pitanja

Ah, I see. Thanks. Guess it's an issue with the extension then.