![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Are the developers of unMHT going to provide a version that will run with your (great, terrific) new Firefox - oh please say yes!
I have thousands of .mht files that I really don't want to open using IE. Also, I seriously don't like the .htm "Web page, complete" save option. It creates (messy) extra folders to hold all the non-htm files. If I want to move an mht file, I have to open & resave it.
選ばれた解決策
No idea, previous Extension discontinued as did not meet enhanced Security for Extensions. It will run on 52.5.0 ESR
What about this, does not say not compatible with ver 57 https://addons.mozilla.org/en-US/firefox/addon/save-page-we/
To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/
Please let us know if this solved your issue or if need further assistance.
この回答をすべて読む 👍 2すべての返信 (10)
選ばれた解決策
No idea, previous Extension discontinued as did not meet enhanced Security for Extensions. It will run on 52.5.0 ESR
What about this, does not say not compatible with ver 57 https://addons.mozilla.org/en-US/firefox/addon/save-page-we/
To submit suggestions for new or changed features, may I suggest: Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/
Please let us know if this solved your issue or if need further assistance.
Irmi1969 said
I have thousands of .mht files that I really don't want to open using IE. Also, I seriously don't like the .htm "Web page, complete" save option. It creates (messy) extra folders to hold all the non-htm files. If I want to move an mht file, I have to open & resave it.
My advice is to install an older version of Portable Firefox and install the unMHT extension; then use "Portable" to read all those saved MHT / MHTML files. That is what I am doing - using an older Firefox installation to read (and save new ones) MHTML files that I have saved over the last 12 years.
https://en.wikipedia.org/wiki/MHTML MHTML format was never approved by W3C as an officially recognized format - it was "proposed" back in 1999 by Microsoft but never got beyond the proposal stage.
Even though Google Chrome and Opera supports that format, Mozilla still refuses to support not official file formats, instead Mozilla has relied upon extensions to provide that capability for Firefox users. But now that MAF and unMHT extensions are dead as of Fx 57, all the previously saved MHT / MHTML files can be read in Fx 57 and later.
And in my experience IE does a poor job of reading MHTML that were created via a Firefox extension; iirc, MAF did a poorer job that unHT did which is why I switched to unMHT from MAF 7 or 8 years ago.
Thank you, guys - much appreciated. In fact, I shall try ALL the solutions offered over a space of time, and see which one runs most smoothly for me. Thank you, Pkshadow! Thank you, the-edmeister!
Hi,
I had problems with FireFox parallel installation.
I decided to install WaterFox and then the .maff and UnMHT add ons.
Note that WaterFox is a bit slow but else works fine.
Pkshadow said
What about this (Save Page WE addon), does not say not compatible with ver 57 https://addons.mozilla.org/en-US/firefox/addon/save-page-we/
Save Page WE can't save multiple tabs, a key feature to me.. I couldn't find any addon with that feature so far. Using UnMHT along with the portable (ESR) version of firefox until then.
この投稿は v00p により
v00p (and Pkshadow), thank you for reminding me about this. I have been dealing with ongoing domestic crises.... I have gone with this solution - installed WE, tried it out and so far so good! Fortunately, I don't need to save multiple tabs. Thanks to all others who replied, too.
I have used Save Page WE for some time and I am not very happy with it. Unlike UnMHT or the Mozilla .maff extesions this add on does not really translate local URLs for use in the downloaded file.
Example:
If one html page contains link references with a #name then this will not be tranlasted for local use.
Down load as an example this link:
http://www.t10.org/lists/asc-num.htm
You will notice that all links in the list are referenced back to the original page, i.e.
http://www.t10.org/lists/asc-num.htm#ASC_02
will stay as such in the locally safed .html file.
This limits the function of Save Page WE significantly.
Thank you for your comments, Michael. I don't think this will be much of a problem for me. Whenever I save a page, I put its original URL into the WE page's comments. So on the rare occasions when I might want to follow a link, I could simply do so via the original page - thanks for the warning.
FYI, I had bad luck with Save WE for this page:
この投稿は bobnn により
bobnn, I understand your frustration. After using WE for a while, I seemed to come across an increasing number of websites that simply left out a lot of bits and pieces during the save. These weren't picked up when I opened them up again, possibly because I hadn't set up something here or there. Though I am moderately software orientated (I'm an old hand at mainframes), I am quite simply not interested in poking around and setting this or that to make things "work" for me. To me, Mozilla is a tool, not a big part of my life. At the moment, I open websites using Mozilla, and if I want to save one, I try to guess whether or not it's going to save nicely with WE. Quite often, I copy and paste the url into IE and save from there. Which is a bit of a hassle and probably not the safest thing to do.