Skip to content
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

Support MHTML #38

Closed
KrasnayaPloshchad opened this issue Dec 16, 2017 · 8 comments
Closed

Support MHTML #38

KrasnayaPloshchad opened this issue Dec 16, 2017 · 8 comments
Labels
won't fix Doesn't fit with the project plans

Comments

@KrasnayaPloshchad
Copy link

Mozilla Archive Format and UnMHT support saving and viewing MHTML format, both of them are wide spread until FF 57.0 released. But Web ScrapBook doesn't support it. MHTML is an open standard formatted in RFC 2557.

@KrasnayaPloshchad KrasnayaPloshchad changed the title Support MHTML while Support MHTML Dec 16, 2017
@danny0838
Copy link
Owner

danny0838 commented Dec 16, 2017

This is currently in our projects.

Although MHTML is an open standard, there are still many issues making supporting MHT difficult. Additionally, MHT support is inconsistent across browsers and is decreasing (Edge, the descendant of IE, stops supporting it; Firefox lost the addon supporting it...).

Grossly speaking, MHT has almost no Advantage over our supported HTZ/MAFF (small size, cross platform, easy restore) and single HTML (convenient in most modern browsers). We have difficulty, are not recommending it, and are not very willing to support it currently.

@danny0838 danny0838 added the enhancement New feature or request label Dec 16, 2017
@cy7yz2rj
Copy link

I agree with disincentivising use of MHTML and preferring MAFF/HTZ over it. Not allowing creation of new .mht files and having only the option of opening already existing ones and possibly converting them to MAFF/HTZ sounds fine.

I have old .mht files that can't be displayed on my offline test browser, QupZilla.
On the other hand, not a single .maff has yet caused any trouble, just unzip and open index.html and everything renders fine on any browser I've tried.

While it is annoying not being able to doubleclick on a .maff and have it automatically open the browser and display the content, the reliability far outweighs the minor inconvenience of manually unzipping.

@danny0838
Copy link
Owner

danny0838 commented Dec 17, 2017

We might implement the feature to view and to convert MHT, but it's of low priority since its usage is deprecated, and existed MHT can be converted to MAFF using the MAF addon anyway (MAF addon is not available in Fx 57+, but one can simply download a portable version of Fx 56 to install it and do the conversion, which is likely a one-time job).

Besides, there's already a solution of viewing a MAFF file directly with double-clicking here.

@KrasnayaPloshchad
Copy link
Author

Here could found some source codes that you can works for this.
http://maf.mozdev.org/installation.html

@danny0838
Copy link
Owner

@KrasnayaPloshchad Thank you for the information. Unfortunately, the technique that MAF addon used for handling MHT are mostly dependent on XUL/XPCOM used in legacy addon API and are no more available in WebExtension.

@danny0838
Copy link
Owner

We know that. UnMHT is also a legacy addon.

@danny0838 danny0838 added the someday Not planned to do in the near future, mostly due to limited resources label Oct 27, 2020
@danny0838
Copy link
Owner

We are not going to implement an ad hoc support to capture a page as MHT format, but may consider implementing a converter for PyWebScrapBook, which will be followed as the new issue in the future.

@danny0838 danny0838 added won't fix Doesn't fit with the project plans and removed enhancement New feature or request someday Not planned to do in the near future, mostly due to limited resources labels Nov 24, 2021
@danny0838 danny0838 mentioned this issue Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
won't fix Doesn't fit with the project plans
Projects
None yet
Development

No branches or pull requests

3 participants